[cinder-csi-plugin] deletionPolicy in values.yaml example

[billerbeck-ou]

/kind bug

What happened:

The example custom StorageClass found in the cinder-csi values.yaml here uses deletionPolicy, and I think it should be reclaimPolicy. Using deletionPolicy seems to still result in the StorageClasses being created, but the policy is ignored.

What you expected to happen:

StorageClasses to be created with the correct reclaimPolicy. This isn't really a problem with the plugin, but the example could be changed.

How to reproduce it:

Use deletionPolicy for custom StorageClasses.

Anything else we need to know?:

First time submitting an issue, so apologies if I overlooked something or this isn't actually a problem!

Environment:

• cinder-csi-plugin version: v1.33.0
• OpenStack version: N/A
• Others:

[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