-
Notifications
You must be signed in to change notification settings - Fork 17
PVC attach/mount failed - csi.storageos.com not found #303
Comments
Hi @sorinpepelea, the microk8s uses an immutable containerised kubelet. It is worth trying the
I don't know for certain if with microk8s the path that should be used is StorageOS and the Kubelet communicate through the CSI socket. So both of them need to be able to see that socket. By adding that Let us know if that is not enough to make it work and we will see if we can look into more specifics. Microk8s is not fully supported at the moment by StorageOS, but we would be open to look into it 😃 |
I could only find "/var/lib/kubelet/plugins_registry/storageos" folder in my system .. I have microk8s installed with snap ..(official instructions) .. there is no '/var/lib/kubelet/plugins/kubernetes.io~storageos' location . if i install storageos with --set sharedDir='/var/lib/kubelet/plugins/kubernetes.io~storageos' , nothing changes, error persists. |
In /var/lib/kubelet/plugins_registry i have a file : |
But my error is csi.storageos.com not found, it does not says csi.storageos.com-reg not found |
Hi @sorinpepelea, I believe microk8s uses the kubelet root dir |
so I should change "--root-dir=${SNAP_COMMON}/var/lib/kubelet" And after a microk8s restart , install storageos ? |
@sorinpepelea Did you tried that options? For etcd I deployed a docker etcd cluster, but would be nice that requirement will be an optional opt-in. |
In a microk8s environment, I installed storageos cluster-operator with helm3 chart , csi enabled .
Everything runs ok , including GUI, and PVC creation.
POD's instead fails to attach - timeout with error : cannot find csi.storageos.com
My install command is as follow :
helm3 install grid-storageos storageos/storageos-operator
--namespace kube-system
--set cluster.kvBackend.address=192.168.0.10:2379 \ # VIP address of external etcd cluster (TLS disabled)
--set cluster.admin.username=storageos
--set cluster.admin.password=********
--set csi.enable=true
--set csi.deploymentStrategy=deployment
--set csi.enableControllerPublishCreds=true
--set csi.enableNodePublishCreds=true
--set csi.enableProvisionCreds=true
The text was updated successfully, but these errors were encountered: