Ensure all containers run with r/o root fs and other std securityContext settings #373
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.
This PR updates the container specs of all ALC deployments to ensure that all containers run with a read-only root filesystem. This is a secure engineering best practice and something users are starting to expect of Kube applications.
The PR also updates securityContext settings at the container and pod levels to bring them into alignment with the standards we are aming for across all things integrated into Stolostron and subsequently RHACM. Some of these settings were already being applied, but inconsistently across the deployments/containers.
Finally, this PR adjusts anti-affinity to conform to key naming that we're using as standard practice for things integrated into Stolostro/RHACM. (These settings are actually being injected this way by the tooling that ingrates things into the MCH operator, but its better that the source-of-truth reflects the settings as desired so there is less "magic" happening via the integration automation.)