-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with applying linstor-csi #187
Comments
It looks like there is no LINSTOR node on the kubernetes node. The CSI plugin expects a LINSTOR Satellite with the same name as the name of the kubernetes node it is running on. |
Hello @WanzenBug
Linstor config:
Storageclass:
PVC:
POD:
Should I install DRBD on Kubernetes nodes too? |
Yes, you need LINSTOR Satellite and also DRBD |
Do I understand correctly that for the CSI driver to work, it is necessary to include the k8s worker node in the Linstor cluster, like satellites? Is there an option to configure the CSI driver without including the k8s worker node in the Linstor cluster? We have an external Linstor cluster. |
Yes, you need both CSI and a running satellite. That satellite can be part of your existing cluster without any storage of it's own. See https://github.com/piraeusdatastore/piraeus-operator/blob/v2/docs/how-to/external-controller.md for an example how to achieve that with the operator. |
If I don't use an operator, is it enough to install the necessary deb packages (Ubuntu) and manually add the k8s worker node host to the Linstor cluster? Need some additional k8s settings? |
Yes, manually installing also works. One thing to keep in mind: the CSI Driver expects the node names in kubernetes (kubectl get nodes) to match the node names in LINSTOR (linstor node list). Keep that in mind. |
Thank you! |
What happens:
Have a separate linstor cluster and try to use it in Kubernetes for PVC.
When try to install the manifest all pods start successfully accept
linstor-csi-node
get the next errors in the containercsi-node-driver-registrar
:Linstor nodes are pingable from kubernetes cluster nodes.
Versions
Kubernetes 1.26.2
linstor 1.16.0
Used manifest - https://github.com/piraeusdatastore/linstor-csi/blob/master/examples/k8s/deploy/linstor-csi-1.19.yaml
only the next is updated in ENV variables
Linstor controller properties:
The text was updated successfully, but these errors were encountered: