Add the ability to include security contexts in container level for cluster checks runners #1598
+28
−2
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.
What this PR does / why we need it:
Which issue this PR fixes
Special notes for your reviewer:
Test plan:
Use the following configuration in your values.yaml:
kubectl get pod <cluster check pod> -o jsonpath='{.spec.containers[*].securityContext}' | jq .
and double check that the security context are appropriately configured in theagent
container.The result should be:
kubectl get pod <cluster check pod> -o jsonpath='{.spec.initContainers[*].securityContext}' | jq .
and double check that the security context are appropriately configured in the init containers.The result should be the following for the
init-config
andinit-volume
init containers:Also check if cluster checks work fine, can set the following to see if the KSM core check works fine as a cluster check
...or use an integration check like Openmetrics.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]
.github/helm-docs.sh
)CHANGELOG.md
has been updatedREADME.md
make update-test-baselines
)