Support setting restrictions on the source for automatically created network policies for services backing webhooks and support setting control plane IPv4 CIDR prefix length for better control-plane matching #307
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
Support setting restrictions on the source for automatically created network policies for services backing webhooks:
The intents-operator may create a network policy for allowing traffic for services backing a webhook.
This new flag will mark the operator whether to restrict this network policy, so only traffic from the control-plane would be allowed, or to allow all services to access the service.
Support setting control plane IPv4 CIDR prefix length:
The nerwork mapper and the intents-operator need to match IP addresses to the control plane on some occasions. For this matching, we are using the CIDR with the prefix length.
On some platform, like GKE, you need to set the prefix length so the matching would recognize a workload as the control plane correctly, for example on GKE https://cloud.google.com/kubernetes-engine/docs/best-practices/networking
References
Checklist