OrangeHRM volume-binding-mode info (#9337)

Signed-off-by: Miguel Martinez <miguel@bitnami.com>
This commit is contained in:
Miguel Martínez Triviño
2018-11-16 14:28:35 -08:00
committed by k8s-ci-robot
parent 5c6ead8772
commit bd333dddea
2 changed files with 3 additions and 2 deletions
+1 -1
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.
+2 -1
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