When mounting two EFS volumes in one deployment, Kubernetes pods get stuck in the Init:0/1 state.

[lbteam001]

The pod becomes stuck in the Init:0/1 state when I try to mount two EFS Volumes in a single deployment. But the Pod starts when I mount just one volume.
I have deployed the Latest version of efs-csi-driver in EKS cluster.

[gkalwig]

What version of K8s do you have? Maybe your error is the same as this one #1245 ? I also had deployments with 2 EFs installed on node where sometimes error occured.

[lbteam001]

Hi @gkalwig
K8s Version= 1.28
Actually, neither the app pod nor the efs pod's logs include any errors. The following warning appears when I describe the app pod:
Error: NodeExpandVolume.NodeExpandVolume failed for volume "pv-logs" : Expander.NodeExpand found CSI plugin kubernetes.io/csi/efs.csi.aws.com to not support node expansion

[srujankujmar]

Even I have faced the same issue

Warning FailedMount 2m58s (x25 over 4m34s) kubelet MountVolume.Setup failed while expanding volume for volume "yggdrasil-inbound-pv" : Expander.NodeExpand found CSI plugin kubernetes.io/csi/efs.csi.aws.com to not support node expansion

Could you please let us know what is the exact issue and what is the ETA for this?

[mskanth972]

NodeExpandVolume is a feature, which certain CSI drivers support, which allows customers to expand their volumes. We do not support this because it doesn't make sense in our case (EFS doesn't have a size limit). And we have that listed in our documentation here.
I think Kubernetes will call this feature if a user tries editing the specification of their Persistent Volume object to increase the size and correct action is taken because it observes that we cannot expand volumes with our driver, and it logs this warning.

[srujankujmar]

we havent modified

NodeExpandVolume is a feature, which certain CSI drivers support, which allows customers to expand their volumes. We do not support this because it doesn't make sense in our case (EFS doesn't have a size limit). And we have that listed in our documentation here. I think Kubernetes will call this feature if a user tries editing the specification of their Persistent Volume object to increase the size and correct action is taken because it observes that we cannot expand volumes with our driver, and it logs this warning.

We haven't modified the size of our pv

[srujankujmar]

NodeExpandVolume is a feature, which certain CSI drivers support, which allows customers to expand their volumes. We do not support this because it doesn't make sense in our case (EFS doesn't have a size limit). And we have that listed in our documentation here. I think Kubernetes will call this feature if a user tries editing the specification of their Persistent Volume object to increase the size and correct action is taken because it observes that we cannot expand volumes with our driver, and it logs this warning.

We haven't modified the size of our pv

[lbteam001]

Hi @mskanth972
Here we are just mounting two EFS Volumes in a single deployment, haven't modified the size of our pv. When we are mounting only one Volume then it's working cool.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten