Lucas Servén Marín

Hi @sepich :) thanks for the PR and for the additional cleanup! Setting the CLI flag on the DaemonSet to disable routing packets over internal IPs entirely effectively turns the...

ah I see! You really just want to have no knowledge of internal IPs at all. Hmm. Does the discovery of internal IPs break things for your network? Maybe internal...

>That means etcd nodes having fast internal interconnection would be encapsulated to VPN. Thanks for explaining. Yes, that's indeed a really good thing to avoid! Normally this would be avoided...

The difference is that when you rely on the standard topology labels you don't need to manually annotate nodes to specify a location, which sounded like an annoying source of...

Hi @tdondich, this sounds very reasonable to me! I envision defining a new annotation that can be added to each individual node to define the egress IP addresses to use...

Thanks for the kind words @tdondich

@tdondich I imagine handling the different cases for egress IPs similar to how the Kubernetes apiserver/controller-manager do: * accept either one ipv4 or one ipv6 or one ipv4 and one...

Regarding tests, the package that will require the most complicated logic is probably the parsing and proper interpretation of the annotations to produce an egress IP data structure on the...

hi @tdondich how is this going? If you're stuck or don't have time to finish that's fine! Let me know and I'd be happy to take over and release this...

Hi @rafi, thanks for raising this issue. Unfortunately, some hosted Kubernetes offerings run the control plane processes in an entirely opaque way without registering any control plane nodes. This configuration...