Remove kolla initialization and reduce SCC from anyuid to nonroot-v2 - #530
Open
dciabrin wants to merge 1 commit into
Open
Remove kolla initialization and reduce SCC from anyuid to nonroot-v2#530dciabrin wants to merge 1 commit into
dciabrin wants to merge 1 commit into
Conversation
Galera pods rely on kolla to initialize: an init container copies config files and generates configs via kolla_set_configs, and a main container uses kolla_start to copy generated configs, set directory permissions, and launch the entrypoint. This requires root privileges and the anyuid SCC. In order to stop requiring special permissions, we no longer rely on Kolla and initialize pods as follows: - The generated config is now an EmptyDir populated by the init container and access by the main container. - Use FSGroup and RunAsUser/RunAsGroup SecurityContext for volume ownership so we no longer need sudo/chown to set up permissions. - Reference TLS certs and operator scripts at their direct mount paths - Add a var-local EmptyDir for password caching previously handled by kolla permission-setting. - Remove remaining references to Kolla, which are no longer needed. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dciabrin The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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
1 participant
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.
Galera pods rely on kolla to initialize: an init container copies config files and generates configs via kolla_set_configs, and a main container uses kolla_start to copy generated configs, set directory permissions, and launch the entrypoint. This requires root privileges and the anyuid SCC.
In order to stop requiring special permissions, we no longer rely on Kolla and initialize pods as follows:
The generated config is now an EmptyDir populated by the init container and access by the main container.
Use FSGroup and RunAsUser/RunAsGroup SecurityContext for volume ownership so we no longer need sudo/chown to set up permissions.
Reference TLS certs and operator scripts at their direct mount paths
Add a var-local EmptyDir for password caching previously handled by kolla permission-setting.
Remove remaining references to Kolla, which are no longer needed.