rbd: use volumeattributesclass feature implement rbd volume qos#6160
Conversation
b78efe5 to
36c1c2f
Compare
c1e4f0a to
dffa21e
Compare
nixpanic
left a comment
There was a problem hiding this comment.
This is a user visible change. Put a note in PendingReleaseNotes.md for this too. Maybe add a note in the main README.md for support of this as well, update other documentation?
|
This pull request now has conflicts with the target branch. Could you please resolve conflicts and force push the corrected changes? 🙏 |
cb885ba to
a8df95a
Compare
|
This pull request now has conflicts with the target branch. Could you please resolve conflicts and force push the corrected changes? 🙏 |
43fa44e to
1a4ade8
Compare
f7b6685 to
e786b28
Compare
nixpanic
left a comment
There was a problem hiding this comment.
Two minor things that caught the eye of Claude Code, and look like good recommendations to me.
|
/test ci/centos/mini-e2e/k8s-1.34 |
e786b28 to
650a107
Compare
nixpanic
left a comment
There was a problem hiding this comment.
Another round of review (now completed by me, not Claude).
These are the only changes I would like to see, everything else looks good to me. Thanks!
b2d68cb to
a79ce62
Compare
Signed-off-by: Yite Gu <[email protected]>
Signed-off-by: Yite Gu <[email protected]>
Signed-off-by: Yite Gu <[email protected]>
Signed-off-by: Yite Gu <[email protected]>
Signed-off-by: Yite Gu <[email protected]>
Signed-off-by: Yite Gu <[email protected]>
Add getCephCSIVersion() that runs "cephcsi -version" in a nodeplugin container and returns the major and minor version numbers. Development builds that report "canary" as the version return math.MaxInt for both so they always compare as newer than any specific release. Add cephcsiVersionGreaterEquals() that wraps getCephCSIVersion() and returns true when the running version is equal to or newer than the requested major.minor version. On failure the test case is marked as FAILED, matching the behaviour of k8sVersionGreaterEquals(). Assisted-by: Claude Code <[email protected]> Signed-off-by: Niels de Vos <[email protected]>
Remove the unconditional setting of controller-modify-secret in createRBDStorageClass() and move it into the VolumeAttributesClass test, where it is actually needed for ControllerModifyVolume calls. Add supportsVolumeAttributesClass() to combine the Kubernetes (>= 1.34) and ceph-csi (>= 3.17) version checks into a single helper. The VAC QoS test uses it as its sole guard condition. When the check passes, the test recreates the default StorageClass with the controller-modify-secret parameters before exercising modify operations, and restores the plain StorageClass afterwards so subsequent tests are not affected. Assisted-by: Claude Code <[email protected]> Signed-off-by: Niels de Vos <[email protected]>
b18b694 to
64998fa
Compare
✅ Branch has been successfully rebased |
|
/test ci/centos/k8s-e2e-external-storage/1.33 |
|
/test ci/centos/k8s-e2e-external-storage/1.34 |
|
/test ci/centos/mini-e2e-helm/k8s-1.33 |
|
/test ci/centos/mini-e2e-helm/k8s-1.34 |
|
/test ci/centos/mini-e2e/k8s-1.33 |
|
/test ci/centos/mini-e2e/k8s-1.34 |
|
/test ci/centos/k8s-e2e-external-storage/1.35 |
|
/test ci/centos/upgrade-tests-cephfs |
|
/test ci/centos/mini-e2e-helm/k8s-1.35 |
|
/test ci/centos/upgrade-tests-rbd |
|
/test ci/centos/mini-e2e/k8s-1.35 |
|
Deprecation notice: This pull request comes from a fork and was queued with |
Merge Queue Status
This pull request spent 23 seconds in the queue, including 3 seconds running CI. Required conditions to merge
|
Describe what this PR does
volumeAttributesClassNamewhen defining the PVC. For example:volumeAttributesClassNameparameter of an existing PVC.ref: https://kubernetes.io/docs/concepts/storage/volume-attributes-classes/
Is there anything that requires special attention
Do you have any questions?
Is the change backward compatible?
Are there concerns around backward compatibility?
Provide any external context for the change, if any.
For example:
Related issues
Mention any github issues relevant to this PR. Adding below line
will help to auto close the issue once the PR is merged.
Fixes: #issue_number
Future concerns
List items that are not part of the PR and do not impact it's
functionality, but are work items that can be taken up subsequently.
Checklist:
guidelines in the developer
guide.
Request
notes
updated with breaking and/or notable changes for the next major release.
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 unrelatedfailure (please report the failure too!)