Add filesystem cache to reduce API calls

[infinite-turtles]

This PR fixes API throttling and provisioning failures that occur during concurrent CreateVolume requests at scale.

The previous implementation scanned all FSx filesystems on every CreateVolume call. This change introduces a local filesystem cache populated by a background poller.

• FindFileSystemByVolumeName now performs a fast lookup against the cache.
• CreateFileSystem and DeleteFileSystem are updated to keep the cache consistent between polls.

Mitigates #469

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: infinite-turtles
Once this PR has been reviewed and has the lgtm label, please assign nckturner for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[linux-foundation-easycla]

• ❌ - login: @infinite-turtles / name: Nico . The commit (a2da25f, b10824a) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please submit a support request ticket.

[k8s-ci-robot]

Welcome @infinite-turtles!

It looks like this is your first PR to kubernetes-sigs/aws-fsx-csi-driver 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/aws-fsx-csi-driver has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @infinite-turtles. Thanks for your PR.

I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[olemarkus]

/ok-to-test

[khoang98]

/test pull-aws-fsx-csi-driver-e2e

[khoang98]

We just merged a fix to the e2e that should resolve the current test issue
/test pull-aws-fsx-csi-driver-e2e

[khoang98]

@infinite-turtles can you sign the CLA auth?

[Trickybrain]

@infinite-turtles
Hey Nico,
Reaching out to you again, can you sign the CLA auth? So we can merge this PR

[infinite-turtles]

Reaching out to our internal OpenSource committee to see if they will authorize the CLA

[Trickybrain]

Hi @infinite-turtles
What is the latest status? Are you able to get to signed?