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
Bug 1954671: disable volume expansion support in vsphere csi driver #24
Bug 1954671: disable volume expansion support in vsphere csi driver #24
Conversation
@dobsonj: This pull request references Bugzilla bug 1954671, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Bugzilla (piqin@redhat.com), skipping review request. 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. |
Skipping CI for Draft Pull Request. |
/test all |
@@ -6,4 +6,4 @@ provisioner: csi.vsphere.vmware.com | |||
parameters: | |||
datastoreurl: "${DATASTORE_URL}" | |||
volumeBindingMode: WaitForFirstConsumer | |||
allowVolumeExpansion: true | |||
allowVolumeExpansion: false |
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.
It could be interesting to add a comment stating why this is currently disabled with a link to the ticket/issue that needs to be fixed.
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.
Also, we need to run make update
to update the bindata file and include that in this PR.
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.
may be we need a verify job to catch failure to run make update
somewhere
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 @bertinatto , updated.
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.
I don't see those limitations were mentioned in the doc like only vSan support it?
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.
actually resize only support block volume, not vSAN, I think.
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.
hmm, so I think at some point this document was changed. But I could confirm with vmware engineers again. In any case - volume expansion is still beta and hence it makes sense for us to keep it disabled until we could test and validate it.
/test all |
1 similar comment
/test all |
/test e2e-vsphere-csi |
Verified that after deploying this change, resize fails with an appropriate error message:
|
/retest |
3 similar comments
/retest |
/retest |
/retest |
814b82d
to
cd7dfdc
Compare
/lgtm |
/retest |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dobsonj, gnufied 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 |
/retest |
/retest Please review the full test history for this PR and help us cut down flakes. |
@dobsonj: All pull requests linked via external trackers have merged: Bugzilla bug 1954671 has been moved to the MODIFIED state. 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. |
No description provided.