Backport of [NET-10547] openshift: re-order SCC volume list for Argo sync into release/1.4.x #4235
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.
Backport
This PR is auto-generated from #4227 to be assessed for backporting due to the inclusion of the label backport/1.4.x.
The below text is copied from the body of the original PR.
Due to logic in OpenShift's admissions hook that force-reorders explicit and implicit entries in this list, our
SecurityContextConstraints
entries will never successfully sync via tools like ArgoCD, which expect an exact input and output match when diff'ing.More details on the problem addressed by this change and potential future improvements to avoid it in the future can be found in #4208 (see comments).
Changes proposed in this PR
volumes
entries to match the post-reconciliation order persisted by OpenShiftHow I've tested this PR
consul-cni
SCC.How I expect reviewers to test this PR
👀
Checklist
Overview of commits