fix: Set securityContext.runAsNonRoot for tuning initContainer
#1163
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.
Setting
statefulset.podTemplate.spec.securityContext.runAsNonRoot: true(spec.template.spec.securityContext.runAsNonRoot: truein STS) will cause the STS pods to fail the startup withCreateContainerConfigError: Error: container's runAsUser breaks non-root policy...error .Since
RunAsUseris already hardcoded to0it seems to make sense to explicitly allow root withrunAsNonRoot: falsefor the tuning initContainerFixes the #1162