Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Add volume capability to ControllerExpandVolume CSI call #70
Add volume capability to ControllerExpandVolume CSI call #70
Changes from 2 commits
64ffa0d
e0df338
f3eb9f7
f745bac
3b462ac
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Given what we have discussed here: https://github.com/kubernetes-csi/external-provisioner/pull/400/files#diff-38b23914da9991d96c9ec4fc3c2525aaR76, should this also be configurable and allow default to be "none"?
@msau42 ^^
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.
For control-plane volume expansion it should not ideally matter. This exists mostly for being on same page as external-attacher , what we really want to pass is block vs fs type.
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.
Let me know if this is okay. Feel free to remove the hold if you are fine with this.
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 think resizer should not have a defaultFSType. Just keep "fsType := pvSpec.CSI.FSType" but don't set a default to be consistent with the proposed change in external-provisioner. Otherwise we could potentially have a default fstype set to ext4 while driver internally use a different type.
In the external-provisioner, if we let driver set default to "none", driver will determine internally what fstype to use.
Unfortunately this fstype is not returned by CreateVolumeResponse in CSI. So pvSpec.CSI.FSType could be not set even if driver has used a non-ext4 type internally. If we change pvSpec.CSI.FSType to ext4 in resizer in this case, that will be the wrong fstype.
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.
okay I have dropped default fstype from 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.
What happens if you call this against a driver that doesn't have this new field?
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.
If the server is compiled (i.e the driver) with a version of CSI which does not have this field then the driver will not simply see it.