New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Relax csiNodeIDMaxLength to longer limit #98753
Conversation
@Jiawei0227: This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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. |
/retest |
1 similar comment
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
/hold
Hold until CSI 1.4 is cut with this change
/hold cancel CSI 1.4.0 has been cut https://github.com/container-storage-interface/spec/releases/tag/v1.4.0 |
/assign @liggitt For API approval |
Update csiNodeIDMaxLength to 192 bytes
/retest |
1 similar comment
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
errorList := validation.ValidateCSINode(newCSINodeObj) | ||
return append(errorList, validation.ValidateCSINodeUpdate(newCSINodeObj, oldCSINodeObj)...) | ||
// in 1.21 on update, set AllowLongNodeID to true only if the old object already has a long node ID | ||
// in 1.22 on update, set AllowLongNodeID=true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
make sure there's a tracking issue open to change this in 1.22
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, I created #99981 for it.
/retest Review the full test history for this PR. Silence the bot with an |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
@ohbus: changing LGTM is restricted to collaborators In response to this:
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. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Jiawei0227, liggitt, ohbus, saad-ali 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:
Approvers can indicate their approval by writing |
With this change, I think the current release note is not correct:
This change will be applicable in 1.22, but in 1.21 the limit is still 128 bytes. |
I updated the release notes. Thanks! |
update error info with the new limit in #98753
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
With CSI spec change in container-storage-interface/spec#464, the length for CSI node id can be extended to 192 bytes. This can unblock users that have a longer csi node id in their CSI driver.
For backwards compatibility, we will break this down to two release. This release we will prepare for the next release change on the actual limits.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
/sig storage
/assign @saad-ali