[Experimental] Use privileged dataplane entrypoint for ingress-gateway #4394
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…d to privileged ports
This will enable a future commit to remove NET_BIND_SERVICE from the widely shared consul.restrictedSecurityContext
nathancoleman
added
the
pr/no-backport
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Note
This PR has a dependency on hashicorp/consul-dataplane#652
Changes proposed in this PR
NET_BIND_SERVICEcapability at runtimeNET_BIND_SERVICEcapability at runtimeHow I've tested this PR
Verify functionality for service mesh with ingress, API, mesh and terminating gateways on both:
How I expect reviewers to test this PR
See above
Checklist