diff --git a/upstreamed/dokuwiki/Chart.yaml b/upstreamed/dokuwiki/Chart.yaml index 93ba4b189..fdca1b2d5 100644 --- a/upstreamed/dokuwiki/Chart.yaml +++ b/upstreamed/dokuwiki/Chart.yaml @@ -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. diff --git a/upstreamed/dokuwiki/README.md b/upstreamed/dokuwiki/README.md index 82895da76..5bdfa164c 100644 --- a/upstreamed/dokuwiki/README.md +++ b/upstreamed/dokuwiki/README.md @@ -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 diff --git a/upstreamed/nats/Chart.yaml b/upstreamed/nats/Chart.yaml index b32483b5b..2bd85505c 100644 --- a/upstreamed/nats/Chart.yaml +++ b/upstreamed/nats/Chart.yaml @@ -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: diff --git a/upstreamed/nats/README.md b/upstreamed/nats/README.md index 5d8f1e841..a524843b0 100644 --- a/upstreamed/nats/README.md +++ b/upstreamed/nats/README.md @@ -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` | diff --git a/upstreamed/nats/templates/statefulset.yaml b/upstreamed/nats/templates/statefulset.yaml index ff615d2ad..46f53ddaa 100644 --- a/upstreamed/nats/templates/statefulset.yaml +++ b/upstreamed/nats/templates/statefulset.yaml @@ -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 }} diff --git a/upstreamed/nats/values-production.yaml b/upstreamed/nats/values-production.yaml index 612668e0e..26981c19a 100644 --- a/upstreamed/nats/values-production.yaml +++ b/upstreamed/nats/values-production.yaml @@ -246,6 +246,9 @@ ingress: # key: # certificate: +# Optional additional arguments +extraArgs: [] + ## Metrics / Prometheus NATS Exporter ## ## ref: https://github.com/nats-io/prometheus-nats-exporter diff --git a/upstreamed/nats/values.yaml b/upstreamed/nats/values.yaml index 7368dc2d7..e9faa9dca 100644 --- a/upstreamed/nats/values.yaml +++ b/upstreamed/nats/values.yaml @@ -250,6 +250,9 @@ ingress: # key: # certificate: +# Optional additional arguments +extraArgs: [] + ## Metrics / Prometheus NATS Exporter ## ## ref: https://github.com/nats-io/prometheus-nats-exporter diff --git a/upstreamed/orangehrm/Chart.yaml b/upstreamed/orangehrm/Chart.yaml index 547e64b3c..f3ab4a804 100644 --- a/upstreamed/orangehrm/Chart.yaml +++ b/upstreamed/orangehrm/Chart.yaml @@ -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. diff --git a/upstreamed/orangehrm/README.md b/upstreamed/orangehrm/README.md index 625389d70..eafa9b28c 100644 --- a/upstreamed/orangehrm/README.md +++ b/upstreamed/orangehrm/README.md @@ -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 diff --git a/upstreamed/owncloud/Chart.yaml b/upstreamed/owncloud/Chart.yaml index 2bf853922..7e4ee0114 100644 --- a/upstreamed/owncloud/Chart.yaml +++ b/upstreamed/owncloud/Chart.yaml @@ -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: diff --git a/upstreamed/owncloud/README.md b/upstreamed/owncloud/README.md index 3e4ad34ed..398e9f6a7 100644 --- a/upstreamed/owncloud/README.md +++ b/upstreamed/owncloud/README.md @@ -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 diff --git a/upstreamed/phabricator/Chart.yaml b/upstreamed/phabricator/Chart.yaml index 1dac4d8f9..32bf8e94e 100644 --- a/upstreamed/phabricator/Chart.yaml +++ b/upstreamed/phabricator/Chart.yaml @@ -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: diff --git a/upstreamed/phabricator/README.md b/upstreamed/phabricator/README.md index 76656413d..d45e70ee7 100644 --- a/upstreamed/phabricator/README.md +++ b/upstreamed/phabricator/README.md @@ -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