k8s-ci-robot
commented
2 months ago @gurskyi277: The label(s) triage/support cannot be applied, because the repository doesn't have them.
In response to [this](https://github.com/kubernetes-sigs/aws-efs-csi-driver/issues/1435):
>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](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
avanish23
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