[openwhisk-deploy-kube] branch master updated: Add description for PVC with static volumes (#741)

[dg...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

dgrove pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/openwhisk-deploy-kube.git


The following commit(s) were added to refs/heads/master by this push:
     new 9f01d17  Add description for PVC with static volumes (#741)
9f01d17 is described below

commit 9f01d17d40d8c15c7f0b9e088a5b4a25d83a089e
Author: Linus Wagner <30...@users.noreply.github.com>
AuthorDate: Thu Aug 11 17:24:05 2022 +0200

    Add description for PVC with static volumes (#741)
---
 helm/openwhisk/README.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/helm/openwhisk/README.md b/helm/openwhisk/README.md
index fe6d6d6..c6f12c7 100644
--- a/helm/openwhisk/README.md
+++ b/helm/openwhisk/README.md
@@ -73,6 +73,7 @@ This chart requires 6 Persistent Volumes to be created to avoid loss of data.  O
 * When the chart is deployed, the value `k8s.persistence.enabled` is set to false to disable usage of Persistent Volumes (for development and test activities).
 * The Kubernetes cluster supports Dynamic Volume Provisioning and has a default StorageClass defined with an associated provisioner.
 * The Kubernetes cluster supports Dynamic Volume Provisioning and when the chart is deployed, the value `k8s.persistence.hasDefaultStorageClass` is set to `false` and `k8s.persistence.explicitStorageClass` is set to a StorageClass which has an associated provisioner.
+* The Kubernetes cluster does not support Dynamic Volume Provisioning and a default StorageClass with an associated provisioner is defined. The PersistantVolumes were created statically. Look at the default values for [persistence.size](https://github.com/apache/openwhisk-deploy-kube/blob/master/helm/openwhisk/values.yaml) to avoid PersistantVolumeClaims to be stuck.
 
 ### PodSecurityPolicy Requirements