rbd: adjust qos parameters start with small case

[YiteGu]

Describe what this PR does

we should change this to small to align this with other parameters.

---

Show available bot commands

These commands are normally not required, but in case of issues, leave any of
the following bot commands in an otherwise empty comment in this PR:

• /retest ci/centos/<job-name>: retest the <job-name> after unrelated
  failure (please report the failure too!)

[iPraveenParihar]

@YiteGu, Can you please add a message in PR description why is this change needed and same in commit message?

[YiteGu]

we should change this to small to align this with other parameters.

updated. the purpose is very simple. change QOS params to small to align this with other parameters.

[nixpanic]

This isn't backwards compatible, is that a problem? Existing StorageClasses with the old parameters won't keep functioning when Ceph-CSI is updated to use the new parameters.

[Madhu-1]

This isn't backwards compatible, is that a problem? Existing StorageClasses with the old parameters won't keep functioning when Ceph-CSI is updated to use the new parameters.

This isn't backwards compatible, is that a problem? Existing StorageClasses with the old parameters won't keep functioning when Ceph-CSI is updated to use the new parameters.

@nixpanic ceph-csi never advertized nbd as supported mounter, its currently kept as alpha feature only https://github.com/ceph/ceph-csi/blob/devel/docs/design/proposals/rbd-nbd.md#status, This change is required to keep all the parameter keys to be inconsistent format.

[Madhu-1]

We can add a release notes to update these keys to switch to the new one.

[nixpanic]

@Mergifyio rebase

[mergify]

rebase

☑️ Nothing to do, the required conditions are not met

• any of:
  • #commits > 1 [📌 rebase requirement]
  • #commits-behind > 0 [📌 rebase requirement]
  • -linear-history [📌 rebase requirement]
• -closed [📌 rebase requirement]
• -conflict [📌 rebase requirement]
• queue-position = -1 [📌 rebase requirement]

[nixpanic]

@Mergifyio queue

[mergify]

queue

✅ The pull request has been merged automatically

The pull request has been merged automatically at 2d95dd3

[ceph-csi-bot]

/test ci/centos/k8s-e2e-external-storage/1.31

[ceph-csi-bot]

/test ci/centos/mini-e2e-helm/k8s-1.31

[ceph-csi-bot]

/test ci/centos/upgrade-tests-cephfs

[ceph-csi-bot]

/test ci/centos/k8s-e2e-external-storage/1.32

[ceph-csi-bot]

/test ci/centos/mini-e2e/k8s-1.31

[ceph-csi-bot]

/test ci/centos/upgrade-tests-rbd

[ceph-csi-bot]

/test ci/centos/mini-e2e-helm/k8s-1.32

[ceph-csi-bot]

/test ci/centos/mini-e2e/k8s-1.32

[ceph-csi-bot]

/test ci/centos/k8s-e2e-external-storage/1.33

[ceph-csi-bot]

/test ci/centos/mini-e2e-helm/k8s-1.33

[ceph-csi-bot]

/test ci/centos/mini-e2e/k8s-1.33

[YiteGu]

We can add a release notes to update these keys to switch to the new one.

Can an existing PVC be switched to a new storageclass by modifying the storageClassName?

[Madhu-1]

We can add a release notes to update these keys to switch to the new one.

Can an existing PVC be switched to a new storageclass by modifying the storageClassName?

its not possible as these attributes are stored in the PV object, best option is to implement VolumeAttributeClass for this one to change the existing options.