fix: helm lint

[oreissig]

What type of PR is this?
/kind bug

What this PR does / why we need it:
We have helm lint running as part of our deployment pipeline. The provided helm chart does not pass this validation without forking and local adjustments, which I'd like to avoid.

helm lint charts/latest/csi-driver-nfs
==> Linting charts/latest/csi-driver-nfs
[INFO] Chart.yaml: icon is recommended
[ERROR] templates/rbac-csi-nfs.yaml: unable to parse YAML: invalid Yaml document separator: kind: ClusterRole

Error: 1 chart(s) linted, 1 chart(s) failed

Which issue(s) this PR fixes:

No known bug exists.

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

none

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: oreissig / name: Oliver Reißig (7374090)

[k8s-ci-robot]

Welcome @oreissig!

It looks like this is your first PR to kubernetes-csi/csi-driver-nfs 🎉. 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-csi/csi-driver-nfs 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 @oreissig. Thanks for your PR.

I'm waiting for a kubernetes-csi 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/test-infra repository.

[andyzhangx]

/ok-to-test

[coveralls]

Pull Request Test Coverage Report for Build 3740707586

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.0%) to 77.209%

---

Totals
Change from base Build 3674305595:	-0.0%
Covered Lines:	603
Relevant Lines:	781

---

💛 - Coveralls

[andyzhangx]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andyzhangx, oreissig

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [andyzhangx]

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

[gazal-k]

could a maintainer please prepare a new release with this change soon?

[andyzhangx]

v4.1.0 should have the right format now

[gazal-k]

v4.1.0 should have the right format now

That was quick. Thank you 🙂