-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Add new topic for expanding PV size #8124
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
Conversation
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.
s/pvc.spec.resources.requests/pvc.spec.resources.requests.storage/
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.
This is shop talk, i dont think its relevant to the end user.
|
@openshift/team-documentation - PTAL. |
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.
Then, the controller applies
(also there may be an extra space between "the" and "controller")
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 wouldn't mention any of the 'internal workings' of this, it will confuse the user.. (no controller, no attributes on PVC objects, nothing on how it works.. this should only show the UX..
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 watches
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.
Would boil this down to say that the PVC status will reflect that the resize is happening (the rest is not end user friendly)
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.
goroutine? Should this be 2 separate words? Not sure what this is.
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.
this should not include discussion of the internals except where they are visible to the user (no mention of controller, goroutine, etc..)
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.
s/plugin/plug-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.
shouldn't mention 'goroutine" and i'd clarrify level-based / edge-based.. thats too shop-talky for end user.
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.
s/plugin/plug-in (a few instances here and across the page)
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.
Shop talk not for end user.
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.
Should the content under "Depending on the volume type" be taken out of the nested list format? I guess it just depends on how it looks when built.
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.
Would only mention the user visible parts here, not controller.. would also re-phrase to remove shop talk.
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.
possible extra space before `pvc.Status.Conditions
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.
Would simplify to only UX and omit the flow/details.
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.
plug-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.
Would remove all shop talk here too. "Once a pod is schedule, the node (avoid kubelet in OSE docs) performs the file system resize is sufficient.
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.
s/loops/cycles (maybe?)
`volume_expand_controller`'s
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.
plug-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.
more shop talk, mention of API or how the controller works should be avoided.
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.
`true`
plug-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.
This is in shop-talk form. It should explain specifically how the feature gate works in OSE (where to add the flag etc..)
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.
`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.
remove "aforementioned"
s/users can/you can
s/their/your
|
This topic needs to be added to the _topic_map.yml file so that it builds as part of the doc set. That will also allow you to run |
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 am still not convinced why should Openshift documentation talk about Kubernetes version. We are introducing Volume expansion as a tech. preview in 3.9, that is what we should document. cc @childsb
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.
+1 with @gnufied .... Everything should be in the context of OSE.
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.
Lets add a new section for Expanding volume types with file system. Such as - EBS, GCE-PD, Cinder and RBD. That section should clearly document 2 step process.
Step 1: Edit your PVC to have new size. User should wait for PVC to have condition PersistentVolumeClaimFileSystemResizePending
Step 2: User can describe the PVC and when the PVC has condition PersistentVolumeClaimFileSystemResizePending then user can (re-)start a pod to finish file system resize of volume on node.
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 appears that we are documenting internals of Volume Expand Controller here. There is no harm in doing that but the top section of this documentation should start with "How to Expand PVCs". Not with how volume expansion works.
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.
We shouldn't have this, only the UX.. it will confuse users.
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.
should only show the UX (user wont know what volume plugin based api call means)
|
I left lots of line item comments, but I dont think these docs have the correct audience... The upstream Kube docs are aimed at platform vendors and deeply technical tire kickers.. Some of the value-add of OSE is making kube user-friendly and much of that is the human-readable/non-geek docs The end-user shouldn't be exposed to any internals, only the UX they will have.. Docs shouldn't mention of kube, or any implementation details, only how to enable & use the feature, or how errors are reported to user. Components should be framed in the context of OSE and use end-user friendly terms.. |
|
@childsb Should we just use the information in the release notes draft? |
|
@tmorriso-rh Yes that's probably good. Maybe add where the error on failure is visible. @gnufied does this feature need to be enabled in 3.9 to use, or is on by default? Are there any extra deployment/setup steps? |
|
Now, according the content of the PR, seems it should be linked to here: https://github.com/openshift/openshift-docs/tree/master/install_config/persistent_storage |
|
@aheslin Ali, can you review this PR to determine where this content should be placed? It's currently targeted for the developer guide. If you need additional details, please see the comments on this Trello card: https://trello.com/c/GdqaM5R3/531-resize-perform-cloudprovider-resize-in-controller |
|
looks good to me from technical point of view. Assigning to @ahardin-rh for further approval. |
|
/lgtm |
|
/assign @ahardin-rh |
|
Bump. @aheslin Ali, can you review this PR to determine where this content should be placed? It's currently targeted for the developer guide. If you need additional details, please see the comments on this Trello card: https://trello.com/c/GdqaM5R3/531-resize-perform-cloudprovider-resize-in-controller @ahardin-rh Ashley, can you review the link to the Admission Controllers topic? Should this be for 3.7 or 3.9? |
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.
@tmorriso-rh This path should be:
xref:../architecture/additional_concepts/admission_controllers.adoc#architecture-additional-concepts-admission-controllers[Admission Controllers]
It is also good to run asciibinder build and test the links in your preview build
|
New changes are detected. LGTM label has been removed. |
|
@gnufied Before merging, can you please verify if this also applies to 3.10, dedicated, or online? Thanks. |
|
@tmorriso-rh it should apply to 3.10 as well. And since online is mostly managed cluster, I am not sure yet if we are going to enable resizing feature in the cluster. I would for now, abstain from making this part of openshift online docs. |
|
/cherrypick enterprise-3.9 |
|
@tmorriso-rh: new pull request created: #8602 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. |
|
/cherrypick enterprise-3.10 |
|
@tmorriso-rh: new pull request created: #8603 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. |
@gnufied @qinpingli PTAL and update as needed. This content was pulled from kubernetes/community#657 and https://kubernetes.io/docs/concepts/storage/persistent-volumes/#expanding-persistent-volumes-claims.
Trello card: https://trello.com/c/e0Awnt9f/771-document-resize-perform-cloudprovider-resize-in-controller