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 experiencing an unexpected behavior with the scheduling process in openEBS lvm-localpv. Even after cordoning node worker-06, new Persistent Volumes (PVs) are still being scheduled on this node.
I was advised by @abhilashshetty04 to create this issue following the discussion in issue #356.
Steps to Reproduce:
Cordon node worker-06 using the command:
kubectl cordon worker-06
Deploy a workload that requires new PVs.
Observe that new PVs are still allocated on worker-06.
Expected Behavior:
New PVs should not be scheduled on a cordoned node, as it is marked as unschedulable.
Actual Behavior:
PVs continue to be provisioned on worker-06 despite it being cordoned.
Description:
I am experiencing an unexpected behavior with the scheduling process in openEBS lvm-localpv. Even after cordoning node
worker-06
, new Persistent Volumes (PVs) are still being scheduled on this node.I was advised by @abhilashshetty04 to create this issue following the discussion in issue #356.
Steps to Reproduce:
worker-06
using the command:worker-06
.Expected Behavior:
New PVs should not be scheduled on a cordoned node, as it is marked as unschedulable.
Actual Behavior:
PVs continue to be provisioned on
worker-06
despite it being cordoned.Environment:
k8s cluster deployed using Kubespray
Debian GNU/Linux 12 (bookworm)
I would appreciate any insights or fixes regarding this behavior. Thank you!
The text was updated successfully, but these errors were encountered: