sam lockart
sam lockart
Seems very similar to an issue I reported https://github.com/containerd/containerd/issues/6772 I've had it trigger without restarting containerd though. Lots of errors about failing to reserve names.
would like to see this feature supported, are we able to reopen?
Thanks for getting back to me and clarifiying @howardjohn and @craigbox. I've tweaked the wording a bit to include envoy's language. As an aside, I had trouble running `make gen`...
Same issue, makes firewalling horrible. Have manually patched kubeconfigs to use private IP... Maybe can override kubeadm args somewhere
> @alam0rt did it helped? It helps, but it gets overridden on upgrade as the kubeadm config is regenerated. For the time being I am just adding the public IPs...
> The admin kubeconfig is generated using value from terraform output `kubeone_api`. By default this value is public IP of the kubeapi loadbalancer. I don't see if `hcloud_load_balancer` can give...
So, it looks like you can use ``` value = { endpoint = hcloud_load_balancer.load_balancer.network_ip } } ``` `network_ip` is defined here: https://github.com/hetznercloud/terraform-provider-hcloud/blob/d6f4207b2b75b76e007bd08602e6dcbfb1740032/internal/loadbalancer/resource.go#L406 but is apparently undocumented!
Speaking of which, is there a good way to regenerate all of the `kubeconfig`s ? I have updated the terraform output and ran `kubeone apply --manifest kubeone.yaml -t new.json` but...
Damn! New cluster it is I guess.