Add note to apply SecurityContextConstraints for OpenShift e2e tests #222
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.
Issue link
What changes have been made
Added a note about a need to create SecurityContextConstraints for KubeRay to use proper user to run Ray cluster.
Without this adjustment the tests using Ray cluster fails on OpenShift.
Verification steps
Install CodeFlare operator using OLM on OpenShift.
Install test requirements by running
make setup-e2e
Run e2e tests - the test
TestMNISTRayJobMCADRayCluster
fails.Apply
SecurityContextConstraints
from this PR into KubeRay operator namespace, respin KubeRay pod.Rerun the tests again - this time all tests pass.
Checks