Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
gurskyi277 opened this issue Aug 9, 2024 · 1 comment

Comments

@gurskyi277
Copy link

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
Copy link
Contributor

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants