Add helm chart support

[wolfgang-desalvador]

What type of PR is this?

Feature

What this PR does / why we need it

This pull request introduces Helm chart support for the Azure Lustre CSI Driver, enabling streamlined installation and management via Helm. It adds comprehensive documentation, chart templates, and configuration files to support both released and development versions of the driver. The changes cover chart packaging, installation instructions, RBAC resources, controller and node deployments, and configuration options.

Helm Chart Introduction and Documentation:

• Added detailed installation and usage instructions for the Azure Lustre CSI Driver Helm chart to charts/README.md, including repo setup, installation methods, upgrade, uninstall, tips, and configurable parameters.

Chart Templates and Kubernetes Resources:

• Added Helm templates for controller deployment, node daemonset, CSI Driver, cluster roles, role bindings, and service accounts to ensure proper permissions for driver operation.

These changes collectively enable users to install, configure, and manage the Azure Lustre CSI Driver using Helm, improving ease of deployment and maintainability.

Which issue(s) this PR fixes:

Fixes #237

Requirements:

• uses conventional commit messages
• includes documentation
• adds unit tests
• tested upgrade from previous version

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

[wolfgang-desalvador]

index.yaml needs to be rebuilt before merging to main and or development

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs 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 PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[dabradley]

/remove-lifecycle stale

I've been updating this for new changes coming in