feat(robot): Support Private Networks & Routing

[jahanson]

When hccm tries to provision and add the server meta data it tries to match the IPs. In my case the main IP is private but as previously stated in a few different issues the robot client can't retrieve vswitch/private IPs so it ultimately fails and ignores provisioning the server metadata even though the hostnames match on robot and on the node.

Is there any way we can ignore the ip matching on robot since the hostname matching is usually enough?

[apricote]

Hey @jahanson,

are you using https://github.com/syself/hetzner-cloud-controller-manager or the unreleased Robot support from this repository?

For the initial version, we will not support using private IPs in clusters with Robot Servers, precisely because we can not get the private IP. The code that fails in your logs is from an official kubernetes library (https://github.com/kubernetes/cloud-provider), so there anything we could do here would be a workaround.

Once we have the initial support released, we can start planning on enabling private networks/vSwitches/Routes. One idea I have right now, would be to let the user set a Node Label for the Private IPs

[jahanson]

Hey @apricote, I am using the unreleased Robot support from this repo. I am currently using cilium between all nodes so disabling the networking function for hccm is no problem. I didn't know however that the logs I provided were from kubernetes/cloud-provider.

Setting a node label for private ips would be great. I appreciate your work on this! If there's anything I can do to help let me know

[apricote]

Great to hear that you are using it already!

The code that fails for you is here: https://github.com/kubernetes/cloud-provider/blob/152995bd25ae20bc618a9ba7039a1b683372c86c/node/helpers/address.go#L131-L134

I plan on talking to the team responsible for Networks next week, to discuss how well we can integrate it. I can not yet promise anything, and it will probably not be included in the next release (planned for the coming week).

[apricote]

Right now it is not possible to configure Routes using vSwitch IPs as Gateway. This is a strict requirement for enabling the Routes functionality.

[github-actions]

This issue has been marked as stale because it has not had recent activity. The bot will close the issue if no further action occurs.