Support applying intents to API server "kubernetes" service, even when it doesn't have a pod #328
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
amitlicht
approved these changes
Jan 7, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
It's a common implementation to have the control plane API server service with no pod, just an endpoint mapped to a server outside of the cluster network. Since egress enforcement requires explicitly enabling access to the API server, this PR allow the user to declare intents to the service in the format:
svc:kubernetes.default, and the result will be an egress network policy to the server IP address and port.Testing
Checklist
Egress network policy is an experimental feature, full documentation will be available on official release.