Bitnami/charts
2
0
Fork 0
mirror of https://github.com/bitnami/charts.git synced 2026-03-05 14:57:31 +08:00
Code Issues Packages Projects Releases Wiki Activity

Synchronize upstreamed folder to 2a48f38ee

Browse Source
This commit is contained in:
bitnami-bot
2018-11-17 10:36:28 +00:00
parent b4988202bc
commit 9d85e7dfe7
13 changed files with 23 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
upstreamed/dokuwiki/Chart.yaml
View File

@@ -1,5 +1,5 @@
name: dokuwiki
version: 3.3.0
version: 3.3.1
appVersion: 0.20180422.201805030840
description: DokuWiki is a standards-compliant, simple to use wiki optimized for creating
documentation. It is targeted at developer teams, workgroups, and small companies.

3
upstreamed/dokuwiki/README.md
View File

@@ -130,7 +130,8 @@ $ helm install --name my-release -f values.yaml stable/dokuwiki
The [Bitnami DokuWiki](https://github.com/bitnami/bitnami-docker-dokuwiki) image stores the DokuWiki data and configurations at the `/bitnami/dokuwiki` and `/bitnami/apache` paths of the container.
Persistent Volume Claims are used to keep the data across deployments. This is known to work in GCE, AWS, and minikube.
Persistent Volume Claims are used to keep the data across deployments. There is a [known issue](https://github.com/kubernetes/kubernetes/issues/39178) in Kubernetes Clusters with EBS in different availability zones. Ensure your cluster is configured properly to create Volumes in the same availability zone where the nodes are running. Kuberentes 1.12 solved this issue with the [Volume Binding Mode](https://kubernetes.io/docs/concepts/storage/storage-classes/#volume-binding-mode).
See the [Configuration](#configuration) section to configure the PVC or to disable persistence.
## Upgrading

2
upstreamed/nats/Chart.yaml
View File

@@ -1,5 +1,5 @@
name: nats
version: 1.3.0
version: 1.3.1
appVersion: 1.3.0
description: An open-source, cloud-native messaging system
keywords:

1
upstreamed/nats/README.md
View File

@@ -81,6 +81,7 @@ The following table lists the configurable parameters of the NATS chart and thei
| `antiAffinity` | Anti-affinity for pod assignment | `soft` |
| `tolerations` | Toleration labels for pod assignment | `nil` |
| `resources` | CPU/Memory resource requests/limits | {} |
| `extraArgs` | Optional flags for NATS | `[]` |
| `livenessProbe.initialDelaySeconds` | Delay before liveness probe is initiated | `30` |
| `livenessProbe.periodSeconds` | How often to perform the probe | `10` |
| `livenessProbe.timeoutSeconds` | When the probe times out | `5` |

3
upstreamed/nats/templates/statefulset.yaml
View File

@@ -89,6 +89,9 @@ spec:
args:
- -c
- /opt/bitnami/nats/gnatsd.conf
{{- if .Values.extraArgs }}
{{ toYaml .Values.extraArgs | indent 8 }}
{{- end }}
ports:
- name: client
containerPort: {{ .Values.clientService.port }}

3
upstreamed/nats/values-production.yaml
View File

@@ -246,6 +246,9 @@ ingress:
# key:
# certificate:
# Optional additional arguments
extraArgs: []
## Metrics / Prometheus NATS Exporter
##
## ref: https://github.com/nats-io/prometheus-nats-exporter

3
upstreamed/nats/values.yaml
View File

@@ -250,6 +250,9 @@ ingress:
# key:
# certificate:
# Optional additional arguments
extraArgs: []
## Metrics / Prometheus NATS Exporter
##
## ref: https://github.com/nats-io/prometheus-nats-exporter

2
upstreamed/orangehrm/Chart.yaml
View File

@@ -1,5 +1,5 @@
name: orangehrm
version: 3.2.1
version: 3.2.2
appVersion: 4.2.0-1
description: OrangeHRM is a free HR management system that offers a wealth of modules
to suit the needs of your business.

3
upstreamed/orangehrm/README.md
View File

@@ -120,7 +120,8 @@ $ helm install --name my-release -f values.yaml stable/orangehrm
The [Bitnami OrangeHRM](https://github.com/bitnami/bitnami-docker-orangehrm) image stores the OrangeHRM data and configurations at the `/bitnami/orangehrm` and `/bitnami/apache` paths of the container.
Persistent Volume Claims are used to keep the data across deployments. This is known to work in GCE, AWS, and minikube.
Persistent Volume Claims are used to keep the data across deployments. There is a [known issue](https://github.com/kubernetes/kubernetes/issues/39178) in Kubernetes Clusters with EBS in different availability zones. Ensure your cluster is configured properly to create Volumes in the same availability zone where the nodes are running. Kuberentes 1.12 solved this issue with the [Volume Binding Mode](https://kubernetes.io/docs/concepts/storage/storage-classes/#volume-binding-mode).
See the [Configuration](#configuration) section to configure the PVC or to disable persistence.
## Upgrading

2
upstreamed/owncloud/Chart.yaml
View File

@@ -1,5 +1,5 @@
name: owncloud
version: 3.3.0
version: 3.3.1
appVersion: 10.0.10
description: A file sharing server that puts the control and security of your own data back into your hands.
keywords:

3
upstreamed/owncloud/README.md
View File

@@ -142,7 +142,8 @@ $ helm install --name my-release -f values.yaml stable/owncloud
The [Bitnami ownCloud](https://github.com/bitnami/bitnami-docker-owncloud) image stores the ownCloud data and configurations at the `/bitnami/owncloud` and `/bitnami/apache` paths of the container.
Persistent Volume Claims are used to keep the data across deployments. This is known to work in GCE, AWS, and minikube.
Persistent Volume Claims are used to keep the data across deployments. There is a [known issue](https://github.com/kubernetes/kubernetes/issues/39178) in Kubernetes Clusters with EBS in different availability zones. Ensure your cluster is configured properly to create Volumes in the same availability zone where the nodes are running. Kuberentes 1.12 solved this issue with the [Volume Binding Mode](https://kubernetes.io/docs/concepts/storage/storage-classes/#volume-binding-mode).
See the [Configuration](#configuration) section to configure the PVC or to disable persistence.
## Upgrading

2
upstreamed/phabricator/Chart.yaml
View File

@@ -1,5 +1,5 @@
name: phabricator
version: 3.3.2
version: 3.3.3
appVersion: 2018.45.0
description: Collection of open source web applications that help software companies build better software.
keywords:

3
upstreamed/phabricator/README.md
View File

@@ -136,7 +136,8 @@ $ helm install --name my-release -f values.yaml stable/phabricator
The [Bitnami Phabricator](https://github.com/bitnami/bitnami-docker-phabricator) image stores the Phabricator data and configurations at the `/bitnami/phabricator` and `/bitnami/apache` paths of the container.
Persistent Volume Claims are used to keep the data across deployments. This is known to work in GCE, AWS, and minikube.
Persistent Volume Claims are used to keep the data across deployments. There is a [known issue](https://github.com/kubernetes/kubernetes/issues/39178) in Kubernetes Clusters with EBS in different availability zones. Ensure your cluster is configured properly to create Volumes in the same availability zone where the nodes are running. Kuberentes 1.12 solved this issue with the [Volume Binding Mode](https://kubernetes.io/docs/concepts/storage/storage-classes/#volume-binding-mode).
See the [Configuration](#configuration) section to configure the PVC or to disable persistence.
## Ingress With Reverse Proxy And Kube Lego