Skip to content

Feat: add support for custom initContainers#32

Open
gsomoza wants to merge 2 commits intoStirling-Tools:mainfrom
gsomoza:gabriel/init-containers
Open

Feat: add support for custom initContainers#32
gsomoza wants to merge 2 commits intoStirling-Tools:mainfrom
gsomoza:gabriel/init-containers

Conversation

@gsomoza
Copy link
Copy Markdown

@gsomoza gsomoza commented Dec 2, 2025

Add the ability to specify custom initContainers via deployment.initContainers
in values.yaml. When specified, custom initContainers override the default
volume-permissions initContainer, providing full flexibility for initialization
logic while maintaining backward compatibility.

Community Note

  • Please vote on this pull request by adding a 👍 reaction to the original pull request comment to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for pull request followers and do not help prioritize the request

Add the ability to specify custom initContainers via deployment.initContainers
in values.yaml. When specified, custom initContainers override the default
volume-permissions initContainer, providing full flexibility for initialization
logic while maintaining backward compatibility.
and improve documentation in values.yaml
@gsomoza gsomoza requested a review from Frooodle as a code owner December 2, 2025 14:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant