Support multiple subnets

[jrouly]

Is your feature request related to a problem? Please describe.

FSx and FileCache only support single AZs. However, my workers on EKS span many AZs. I would like for the CSI driver to be able to create a PVC backed by FSx in any of the available subnets for the cluster.

Describe the solution you'd like in detail

• Provision one SC backed by the fsx-csi-driver with multiple subnets or a subnet selector specified.
• When a pod is created using the SC, any of the available subnets can be selected to provision the FSx volume and the pod will be scheduled in the selected subnet.

Describe alternatives you've considered

The current strategy means that every workload scheduled to use the fsx CSI driver will be scheduled in a single AZ. This will cause pretty severe imbalance on my EKS cluster.

[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