-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HostEndpoint node selector + interface name regexp #8840
Comments
@jonas-jasas could you provide some more details about what you are looking for here?
|
Each node has 4 network interfaces, so I have to create 40 |
Have you considered Calico's auto host endpoint feature? https://docs.tigera.io/calico/latest/network-policy/hosts/kubernetes-nodes#automatic-host-endpoints Calico can create a single host endpoint per-node that represents all interfaces on the node. |
Is it possible to classify which interface is external which internal using auto host endpoint feature? In my case I do this:
|
Ah right. No, if you want to be able to treat different interfaces on the same node differently, then today you would need to create HEPs for each. I think it would be a nice enhancement if we did what you originally suggested, then - a node selector and regex matching on interfaces. |
Feature request
To reduce
HostEndpoint
resource count in case of multiple node scenario, would be great to haveHostEndpoint
node selector (based on k8s labels) and interface name match using regexp.The text was updated successfully, but these errors were encountered: