Backport of Support restricted PSA enforcement part 2 into release/1.0.x #2740
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 #2702 to be assessed for backporting due to the inclusion of the label backport/1.0.x.
🚨
The person who merged in the original PR is:
@pglass
This person should manually cherry-pick the original PR into a new backport PR,
and close this one when the manual backport PR is merged in.
The below text is copied from the body of the original PR.
Changes proposed in this PR:
Part 2 of #2572.
Update the following to set a "restricted" security context:
mesh-gateway-deployment.yamlAlso, fix a WAN federation test to run on kind
How I've tested this PR:
Run acceptance tests on kind with restricted PSA enforcement enabled on the consul namespace (see script)
Test script:
make kind
and then./test-psa-kind.sh
(no tproxy) or./test-psa-kind.sh -tproxy
(tproxy enabled). Toggle comments at the bottom to try to run other tests.make kind-cni
and./test-psa-kind.sh -cni
to test with tproxy+cniTest script
How I expect reviewers to test this PR:
Checklist:
Overview of commits