You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using openEBS localpv LVM with a StorageClass with Custom Node Labels (for all my worker nodes). However, volumes are always provisioned on node worker-01, and if I cordon worker-01 volumes will never be scheduled on different nodes.
workaround : if I create a new storage class for a specific node (other than worker-01) the volume is provisioned without any problem.
I am using openEBS localpv LVM with a StorageClass with Custom Node Labels (for all my worker nodes). However, volumes are always provisioned on node worker-01, and if I cordon worker-01 volumes will never be scheduled on different nodes.
workaround : if I create a new storage class for a specific node (other than worker-01) the volume is provisioned without any problem.
here is my storage class:
kubectl logs -f openebs-lvm-localpv-controller-7b6d6b4665-fk78q -n openebs -c openebs-lvm-plugin
https://gist.github.com/khalMeg/ff579367b9ad5c0d5016841b3607aa8a
kubectl logs -f openebs-lvm-localpv-node-[xxxx] -n openebs -c openebs-lvm-plugin
https://gist.github.com/khalMeg/cd740b62d5102d61e99160bbb8212cac
Environment:
k8s cluster deployed using Kubespray
Debian GNU/Linux 12 (bookworm)
The text was updated successfully, but these errors were encountered: