Add commands to modify Openshift secure contexts #250
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
I had issues with getting the pods up and running. turns out it was the secure contexts, and once I set the secure context to anyuid all pods were able to start successfully.
fixed spelling of Prometheus
Found that the official Openshift Istio documentation mentions executing a single command to modify security contexts for all service accounts within a namespace. https://istio.io/docs/setup/platform-setup/openshift/
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.
After deploying to Minishift 3.11, several of the pods refused to start, unable to write to their root fs. After some investigation, found that the SCC's needed to be changed. It was missing the command for Prometheus, so I added that.