CrashLoopBackOff for hcloud-csi-controller with "Failed to connect to the CSI driver" #742
Labels
question
Further information is requested
Comments
|
Hi, to assist you with your issue, I’ll need a bit more information.
If you do not want to publicly share your logs, you can also open up a customer support ticket and reference this issue there. https://console.hetzner.cloud/support Best Regards |
|
Hi @lukasmetzner thanks for the reply , I am running Kubernetes version 1.29. This was the script I used with some unrelated parts omitted: # Apply Hetzner Cloud Secrets
$KUBECTL apply -f - <<EOF
apiVersion: v1
kind: Secret
metadata:
name: hcloud
namespace: kube-system
stringData:
token: "$hcloud_token"
EOF
# Apply Hetzner Cloud CSI and CCM manifests
kubectl apply -f https://raw.githubusercontent.com/hetznercloud/csi-driver/main/deploy/kubernetes/hcloud-csi.yml
kubectl apply -f https://github.com/hetznercloud/hcloud-cloud-controller-manager/releases/latest/download/ccm.yaml
kubectl -n kube-system patch ds kube-flannel-ds --type json -p '[{"op":"add","path":"/spec/template/spec/tolerations/-","value":{"key":"node.cloudprovider.kubernetes.io/uninitialized","value":"true","effect":"NoSchedule"}}]'Here is the log output from all containers: Will be grateful for any ideas on how to move forward from this. Thank you |
|
Hey, could you please provide some more information by:
You could also enable debug logs via the environment variables: In general the issue is related to the csi-driver container not starting correctly. As a result the unix socket is not created and the liveness probe fails and other related containers are not working correctly. Best Regards |
|
Having the same issue. |
|
I'm having the same problem. |
|
What helped me is providing the right kubelet args and having hccm properly installed.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment:
Kubernetes version: 1.2.9
Hetzner Cloud CSI Driver version: latest
Pod affected: hcloud-csi-controller
Namespace: kube-system
Problem:
I am facing an issue where the hcloud-csi-controller pod goes into CrashLoopBackOff. 4 of the containers are consistently crashing, and logs show the following error message:
The pod status indicates that only 1 out of 5 containers are running, with 4 stuck in a crash loop.
Setup:
This is how I set up the CSI and Cloud Controller Manager:
The text was updated successfully, but these errors were encountered: