Closed tmojzes closed 3 months ago
@tmojzes Did you get this running?
@lieberlois Unfortunately not, I have tried today with the latest version of the providers but failed like before. Have you tried it yourself?
@tmojzes Tried it aswell, didnt work. I also didnt get other bootstrap providers (k3s in my case) running with this hetzner infrastructure provider
Unofficial feedback from me (Syself employee): We currently see no benefit in supporting Talos. I personally like it, but overall we are happy with kubeadm and debian/ubuntu based images.
Dear Talos friends. Feel free to create a new project at Github which explains how to use caph together with Talos. We (Syself) won't invest time in the next months.
Remember: "Yes" is forever, and "no" is temporary.
If you provide good docs how to do that, then we might switch.
Afaik the Go-code of caph does not need to be changes to support Talos.
If you have particular issues with using talos bootstrap provider together with caph, then please open a new issue. Thank you.
/kind bug
What steps did you take and what happened:
I am trying to set up a k8s cluster on Hetzner but it fails.
Commands used for cluster setup:
Local bootstrap cluster setup:
Commands used for creating a Talos cluster on Hetzner:
kubectl create secret generic hetzner --from-literal=hcloud=$HCLOUD_TOKEN --from-literal=robot-user=$HETZNER_ROBOT_USER --from-literal=robot-password=$HETZNER_ROBOT_PASSWORD
kubectl create secret generic robot-ssh --from-literal=sshkey-name=cluster --from-file=ssh-privatekey=$HETZNER_SSH_PRIV_PATH --from-file=ssh-publickey=$HETZNER_SSH_PUB_PATH
Patch the created secrets so they are automatically moved to the target cluster later.
kubectl patch secret hetzner -p '{"metadata":{"labels":{"clusterctl.cluster.x-k8s.io/move":""}}}' kubectl patch secret robot-ssh -p '{"metadata":{"labels":{"clusterctl.cluster.x-k8s.io/move":""}}}' kubectl apply -f talos-cluster.yaml
Caph controller version: v1.0.0-beta.19 Logs:
Cabpt controller version: v0.6.1 Logs:
Cacppt version: v0.5.2 Logs:
Talos logs:
What did you expect to happen: A working cluster that can be reached with kubectl and talosctl on the loadbalancer's public IP.
Environment:
cluster-api-provider-hetzner version: caph:v1.0.0-beta.19
Kubernetes version: Client Version: v1.28.0 Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3 Server Version: v1.27.4+k3s1
OS: Pop!_OS 22.04 LTS