Add Volume permissions initContainer Toggle #75
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While attempting to use this Chart on openshift, I discovered that OpenShift's built-in Security Context Contraints make the
SecurityContextsetting for this chart unnecessary and when using with persistent storage there is no way to disable the init container responsible for configuring the/storagemount's permissions. With a default security context, no processes can run as root and executechmod's orchown's to change the permissions of/storage.As such, on openshift (and maybe other k8s distros), the permissions init container isn't necessary. This PR adds a boolean toggle for disabling this in the deployment template.
Here's an example of installing this chart with persistent storage on openshift: