Update SCCs to match Security Context #950
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
chrismuellner
changed the title
mjgrzybek
reviewed
Jul 12, 2022
...g/helm/chart/default/templates/Openshift/oneagent/securitycontextconstraints-privileged.yaml
Show resolved
Hide resolved
chrismuellner
approved these changes
Jul 12, 2022
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
The SCCs were not "matching enough" to what the actual securityContexts we had on the deployments, so openshift couldn't/wouldn't match them, so it errored.
How can this be tested?
Deploy it on Openshift, and everything should work
Checklist
[ ] Unit tests have been updated/added