Spike in EFS client connections after upgrading from version 1.7.7 to version 2.0.6

[gurskyi277]

We noticed that after updating the add-on of aws-efs-csi-driver from version 1.77 to version 2.0.6 on our EKS cluster, there was an increase in client connections to the EFS, which is simultaneously mounted to several of our services running in EKS.

In version 1.7.7, there were 2 client connections regardless of the number of pods using EFS. After upgrading to version 2.0.6, the number of connections increased, proportional to the number of pods using EFS multiplied by 2.

This is not an issue, but we would like to understand if this is the correct behavior after the driver update, or if it might be a misconfiguration on our part.

/triage support

[k8s-ci-robot]

@gurskyi277: The label(s) triage/support cannot be applied, because the repository doesn't have them.

In response to this:

We noticed that after updating the add-on of aws-efs-csi-driver from version 1.77 to version 2.0.6 on our EKS cluster, there was an increase in client connections to the EFS, which is simultaneously mounted to several of our services running in EKS.

In version 1.7.7, there were 2 client connections regardless of the number of pods using EFS. After upgrading to version 2.0.6, the number of connections increased, proportional to the number of pods using EFS multiplied by 2.

This is not an issue, but we would like to understand if this is the correct behavior after the driver update, or if it might be a misconfiguration on our part.

/triage support

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[avanish23]

/kind support

[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