[helm] Add volume management, custom labels, environment variables and custom existing secret #108
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.
Hello, 👋
Thanks for your work on this operator, it's very useful!
We installed it on our EKS cluster using Helm after some tweaking to make it work with AWS-flavored Kubernetes components (most notably the CSI driver for AWS secrets and the CNI), here they are in this PR.
Context
SecretProviderClass
(see documentation), which will create a secret with some needed keys.SecurityGroupPolicy
, we want to be able to add custom labels onto our pods since it applies to pods with amatchLabels
(see documentation)Changelog
volumes
andvolumeMounts
in Helm chart, to declare and mount volumes on the pod.podLabels
to add custom labels on the pod.env
to specify additional environment variables injected in pod.existingSecret
to specify an already existing secret where the operator may fetch its environment variables (this will not create a new secret).tolerations
andnodeSelector
to make it possible to manage more precisely where the pods are scheduled.I am unsure as to how to bump the version.
Let me know if there is anything incorrect, I'll be happy to update it.
Thanks!