I'm having trouble with my cluster not being able to create volumes, and I'm not sure what to do next. Specifically, I have set up a PersistentVolumeClaim (PVC) named 'longhorn-test' in the default namespace, using the Longhorn storage class. However, its status is pending, and there are several warning events indicating a problem with provisioning. It seems that the `spec.drivers` is showing as null, which I suspect might be the issue. I checked the CSINode output and noticed something seems off with the drivers. Longhorn version is 1.10.2, and the configuration appears correct. I'm open to suggestions on where to look or what changes to make. I've also got additional logs if needed.
3 Answers
Depending on your operating system, ensure that both open-iscsi and nfs-utils are installed and running on your nodes. Longhorn can have issues if those dependencies aren't present, which could be causing your problems.
You might be missing the `topology.kubernetes.io/zone` labels on your nodes. If you requested cross-zone replication, that could definitely lead to issues. Make sure your node labels are set correctly.
It sounds like the CSI node driver may not have registered properly with the kubelet on your node, which could explain the null drivers issue. I'd recommend checking the logs of the node-driver-registrar container in the Longhorn CSI plugin pod on that specific node. Those logs should provide some insight into any registration failures.
Related Questions
How To Get Your Domain Unblocked From Facebook
How To Find A String In a Directory of Files Using Linux