-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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
Adding content for allowVolumeExpansion field in StorageClass #15604
Conversation
Deploy preview for kubernetes-io-master-staging ready! Built with commit 94c92c9 https://deploy-preview-15604--kubernetes-io-master-staging.netlify.com |
/assign @Rajakavitha1 |
thanks for fixing this. lgtm note: please squash the commits into one. |
@poothia I have squashed all the commits related to allowVolumeExpansion into one. Should I squash all the commits that are showing up in this PR into one? Apologies for a lot of commit and amends, this is my second PR and I am still learning. |
/lgtm thanks @snathan13 |
/assign @gnufied |
good catch, thanks @msau42 |
The following types of volumes support volume expansion, when the underlying | ||
Storage Class has the field `allowVolumeExpansion` set to true. | ||
|
||
* gcePersistentDisk |
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.
@gnufied, can you verify which version all of these plugins were implemented in?
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.
ping @gnufied for confirmation :)
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.
here is support/version matrix of various volume types look like:
- EBS (1.11)
- Cinder (1.11)
- Glusterfs (1.11)
- GCE PD (1.11)
- Portworx (1.11)
- Azure File (1.11)
- RBD (1.11)
- Azure Disk(1.11)
- Flex Volume (1.13)
- CSI (1.14, 1.15 - Alpha, 1.16 beta)
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 might be worth updating this document and explicitly specify which version of k8s the volume plugin type supported expansion.
@snathan13, Sorry for the late reply. Yes you should squash all the commits for this change and mention all the changes you made in one commit. As it will help in keeping git history concise and clean. We should make multiple commits only when there are a lot of changes in multiple files to make reviewing easy.
Please don't apologise, Even I am still learning! |
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.
@snathan13 Thanks for this PR! ✨ You're off to a good start. Be sure to respond to reviewer feedback and squash your commits. 👍
This lgtm but would like @gnufied to confirm the releases where each of the plugins were implemented. |
it's been 19+ days. let's merge and iterate /approve |
/assign @Rajakavitha1 |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dims, jimangel 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 |
I will create another PR with changes that @gnufied mentioned in the comments above. |
This PR is in reference to issue - #15587. I have added allowVolumeExpansion in the example and have written a paragraph to explain what it is. I have added supported types and a note telling that it cannot be used to shrink volumes. Please review and help me correct if any of the content is not up-to date and if anything else is missing. Thanks!