fix: bbolt data directory permissions #151
Merged
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
This PR updates the ownership and permissions for the
bbolt
data directory. It's configured to only add the necessary script (via a configMap) andinitContainer
if the backend is of typebbolt
.Based on the ticket, it's a little unclear to me whether or not these changes need to be applied to other deployments. The slack messages refer only to the bindplane container, I believe, so I started with that. It's also a bit unclear if we actually want to update the
containerSecurityContext
defaults.Screenshot of the permissions when running locally on
minikube
withbbolt
as backend:Please check that the PR fulfills these requirements