Fix(core): Openshift securityContext on global operator #4932
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
oscerd
approved these changes
Nov 27, 2023
squakez
approved these changes
Nov 28, 2023
In global mode the integration pod securityContext needs to be generated from the integration namespace.
gansheer
force-pushed
the
fix/openshift_secconstraint_integration_pod
branch
from
23317f0
to
78e31c8
Compare
|
Is this ready to merge? |
Yes |
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.
In global mode the integration pod securityContext needs to be generated from the integration namespace.
Test done on global/non-global operator deployment on OCP 4.12.13
Release Note