feat(csi): add OpenStack Manila CSI driver support

[jgo3364]

• Add core Manila CSI driver roles (controller, nodeplugin, RBAC)
• Add persistent_volumes role to deploy the storage class
• Register provider-os container images and version tags in defaults

What type of PR is this?
/kind feature

What this PR does / why we need it:

This PR introduces support for the Manila CSI driver within Kubespray to enable OpenStack shared filesystem storage provisioning.

Key changes:

• Add core manila CSI driver roles (controller, nodeplugin, RBAC)
• Add persistent_volumes role to deploy the storage class
• Register provider-os container images and version tags in defaults

Which issue(s) this PR fixes:

Special notes for your reviewer:

This is my first pull request here!
This implementation is currently being tested and validated in a client environment, and the manila CSI volume provisioning has been successfully verified.

Please let me know if any ansible adjustments or formatting fixes are needed!

Does this PR introduce a user-facing change?:

Add core Manila CSI driver roles and storage class deployment support.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: jgo3364 / name: GONTHIER Jeremy (29f04c1)

[kubernetes-prow]

Welcome @jgo3364!

It looks like this is your first PR to kubernetes-sigs/kubespray 🎉. 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/kubespray 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 @jgo3364. Thanks for your PR.

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

[kubernetes-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jgo3364
Once this PR has been reviewed and has the lgtm label, please assign tico88612 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

[yankay]

/ok-to-test

[tico88612]

@jgo3364 Can we use a Helm Chart for this? I'm not a fan of us maintaining the entire YAML configuration.