inject init-container secrets webhook #944
Closed
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 this PR does:
Changes the default secrets-webhook to inject an init-container into each pod that is eligible for mutation through the secrets injection annotation. The webhook will insert the init-container into the first position of each pod since some init-containers might depend on the credentials being available on the local filesystem (e.g. medusa restores). By default, the webhook will inject the
k8ssandra/k8ssandra-client
image, which will have a mount command to process the annotation string, retrieving and mounting the secrets to the specified path. If a user wants to use their own custom image, they can set the annotationk8ssandra.io/inject-secret-image
with the image name. The custom image must be compatible with the args["mount", {secretInjection}"]
Which issue(s) this PR fixes:
Fixes #605
Checklist