feat: Optional arbitrary init containers #192
Merged
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
Dylan-M
approved these changes
Dec 17, 2024
jsirianni
deleted the
joesirianni/bpop-1461-helm-support-extrainitcontainers
branch
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.
Description of Changes
Added support for initContainers. Each deployment has its own section. See the change to
test/cases/nats/values.yamlfor an example.Init containers will allow users to perform custom actions before starting each service. Most users will not rely on this feature, it is for more advanced use-cases or testing.
e.g. I will be using this feature for generating certificates at startup, using
openssl.Testing
I updated
test/cases/nats/values.yamlto deploy initContainers. Working great. Each pod has its own basic init container.Please check that the PR fulfills these requirements