nfs-controller pods stuck in pending

417 views
Skip to first unread message

Jared Ga-Inai

unread,
Jul 17, 2022, 3:14:28 PM7/17/22
to kubernetes-sig-storage
Hi,

I am trying to deploy this for the first time but my controller pods are stuck in pending status because of "0/5 nodes are available: 5 node(s) didn't match Pod's node affinity/selector."

I deployed it through helm with the setting "--set controller.runOnControlPlane=true" and as far as I can tell, that should work. All my master nodes have "node-role.kubernetes.io/cont
rol-plane=true" set.

Does anyone know what could be the problem here?

This is the full deploy command I used:
helm install csi-driver-nfs csi-driver-nfs/csi-driver-nfs \
--namespace nfs-provisioner \
--version v4.1.0 \
--set controller.runOnControlPlane=true \
--set controller.replicas=2

Jared Ga-Inai

unread,
Jul 18, 2022, 12:36:53 AM7/18/22
to kubernetes-sig-storage
Ended up redeploying with "--set controller.runOnControlPlane=true" removed and it works now. That option is just broken (and the master equivalent as well). This mailing list seems kind of dead, but hope someone sees it.

Michelle Au

unread,
Jul 18, 2022, 2:47:18 PM7/18/22
to Jared Ga-Inai, kubernetes-sig-storage
Hi Jared,

Thanks for reporting this issue. Can you also open an issue in the github repo so the maintainers can take a look at it?

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-storage" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-st...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-storage/84115cfb-febc-4dd2-8e55-18e3f116583fn%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages