#Hi Support
1 messages · Page 1 of 1 (latest)
Hi @whole nimbus, the Trident daemonset pod on each worker node does not communicate with ONTAP via the ONTAP management LIF. The Trident Controller uses the management LIF to make calls to ONTAP. The daemonset pod needs to have access to mount NFS volumes or attach iSCSI volumes via the data LIF
@tall pasture Thanks for your reply.
So if one worker node without daemonset pod due to whatever reasons, is it still able to mount NFS volumes for ontap_nas driver assuming this node can communicate the data LIF? Thanks.
If the Trident daemonset pod isn't running on a worker node then Kubernetes won't schedule a Pod to that worker node that has a Trident volume attachment.