Add init containers #258
Merged
Add init containers #258
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… dynamic configuration use cases.
|
|
jasonodonnell
approved these changes
May 8, 2020
radudd
pushed a commit
to radudd/vault-helm
that referenced
this pull request
Jun 5, 2020
… dynamic configuration use cases. (hashicorp#258)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This merge request would allow the operator to define her own init containers. This would support use cases like TLS certificate introduction without requiring TLS private keys in Terraform state, for example. This would also support other use cases that need to inject configuration only known at pod runtime.