Simon Ostendorf

> Yes, it does work including networking and routes out of the box when using [hetzner-k3s](https://github.com/vitobotta/hetzner-k3s) tool. But I had issues with getting HCCM to recognize the nodes when defining...

If you see `failed to get node address from cloud provider that matches ip: 10.x.x.x, requeuing` you have to enable routes-controller with `network.enabled=true`.

What needs to be done to enable route controllers with robot support? Is this generally supported by the underlying network and does the support need to be implemented in the...

> As far as I know the routes table in the network configuration is not compatible with vSwitch. But I think it should be possible to use private ip addresses...

> As far as I know the routes table in the network configuration is not compatible with vSwitch. I found the following configuration: https://registry.terraform.io/providers/hetznercloud/hcloud/latest/docs/resources/network#expose_routes_to_vswitch. This tells me that routes should...

@apricote @janiskemper did you already thought about a migration path? I think the "old" variant with `bm-` in the hostname and the provider id should be completely replaced with no...

> [@simonostendorf](https://github.com/simonostendorf) we at Syself have the wish to migrate to the "official" one at one point, but did not spend the time on developing or testing a clear migration...

I think Phase 1 and 2 can be performed together, so that new nodes automatically get the hrobot provider id and the old variant is only for old nodes.

> Hi, what is the state of this issue? > @simonostendorf do you still have it in your todo list? Yes but not with prio and my todo list is...

> not sure if qemu-img is available there right now I checked for that and the rescue system contains `qemu-img`, so implementing this shouldnt be a problem.