[manila-csi-plugin] Support mutable NFS access rules

[taaahaaa]

What this PR does / why we need it:

Adds support for updating Manila NFS share access rules after a PVC has been provisioned. The Manila CSI plugin now advertises the CSI MODIFY_VOLUME controller capability for NFS and implements ControllerModifyVolume so changes to nfs-shareClient through a VolumeAttributesClass reconcile the share's rw IP access rules.

The reconciliation is idempotent, grants and activates new rules before removing obsolete rules, waits for revocations to complete, and preserves read-only and non-IP rules. Mutable parameters are also honored during initial volume creation.

The Helm RBAC grants access to VolumeAttributesClass resources, and the Manila CSI documentation includes an example.

Which issue this PR fixes(if applicable):

Fixes #3226

Special notes for reviewers:

Validated with:

• go test ./pkg/csi/...
• go vet ./pkg/csi/manila/...
• helm lint charts/manila-csi-plugin
• git diff --check

Release note:

[manila-csi-plugin] Support updating NFS share client access rules through VolumeAttributesClass.

[kubernetes-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Details

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

[kubernetes-prow]

Welcome @taaahaaa!

It looks like this is your first PR to kubernetes/cloud-provider-openstack 🎉. 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/cloud-provider-openstack 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. 😃

[kubernetes-prow]

Hi @taaahaaa. Thanks for your PR.

I'm waiting for a kubernetes 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.

Details

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.

[gouthampacha]

/ok-to-test

[taaahaaa]

All required checks are passing, and this is ready for review. @gouthampacha @kayrus, could you please take a look when you have time?