search

syself / cluster-api-provider-hetzner

Cluster API Provider Hetzner :rocket: The best way to manage Kubernetes clusters on Hetzner, fully declarative, Kubernetes-native and with self-healing capabilities
https://caph.syself.com
Apache License 2.0
680 stars 60 forks source link

ccm-hetzner is failing to start #1476

Open Aman1994 opened 2 months ago

Aman1994 commented 2 months ago

/kind bug

What steps did you take and what happened: Error: secret "capi-cluster-hetzner" not found

What did you expect to happen: Expected the pods to run but instead it fails with . It was getting created automatically before . This secret is indeed present in my management cluster and was getting copied to my workload cluster automatically and I could see that in kube-system NS - but it doesn't get created anymore. 

Error: secret "capi-cluster-hetzner" not found

Environment:

guettli commented 2 months ago

Please elaborate where you get this error message.

Maybe the secret is in the wrong namespace? Try kubectl get secret -A

Can you please run this tool to see which Conditions indicate an unhealthy state (one time in the mgt-cluster, one time in the wl-cluster).

go run github.com/guettli/check-conditions@latest all

What do you mean with "but it doesn't get created anymore."?

Where do you define the string "capi-cluster-hetzner" (because we don't use a secret with that name by default)?