helm chart - add support for emptyDir storage type #5610
Merged
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.
What problem are we solving?
Currently, the supported storage types are either persistent, or
hostPath
, so for ephemeral storage generallyhostPath
is used (e.g. logs storage).hostPath
mounts a directory from the host node's filesystem and can pose a security risk on shared/multi-tenant k8s clusters, so its usage is often restricted.Adding support for
emptyDir
storage gives another option for ephemeral storage, which does not pose a security risk on shared/multi-tenant K8s cluster, so is generally allowedHow are we solving the problem?
Adding support for the
emptyDir
storage type in all places that allow defining a storage type.This PR introduces
emptyDir
as a new option, and if it's not explicitly used in thevalues.yaml
file, it has no effect on existing users.How is the PR tested?
Tested a deployment on a local K8s cluster, verifying that volumes were created as
emptyDir
when configured for it, uploading and downloading filesChecks