feat: support additional pod containers - #297
Open
cptjacky wants to merge 1 commit into
Open
Conversation
|
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 team!
Why
I want to play around with deploying a https://github.com/Altinity/clickhouse-backup container alongside the server pods so we can do backups from disk directly.
I believe this can also be an useful configuration to expose.
What
Added a
Containerskey in the already existingPodTemplateSpec, following the same logic asInitContainers(which actually can be used as a "hack" with the newrestartPolicy: Alwaysbut this isn't ideal for production use.I tested a local install of the modified operator and it managed to launch the clickhouse-backup extra container.
Happy to iterate on this if this is missing/not ok!