Open sftim opened 2 years ago
Remember to update https://kubernetes.io/docs/concepts/storage/volume-snapshots/ if you make any relevant changes.
/sig storage
/triage accepted
@sftim Are we eyeing at creating seperate pages, each for a task like:
and others? I personally believe a nice way would be to create 1-page with a list of all these tasks, I am still a bit confused about approaching this issue though.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
@sftim Are we eyeing at creating seperate pages, each for a task like:
* https://kubernetes.io/docs/concepts/storage/persistent-volumes/#create-persistent-volume-claim-from-an-existing-pvc * https://kubernetes.io/docs/concepts/storage/persistent-volumes/#create-persistent-volume-claim-from-volume-snapshot * https://kubernetes.io/docs/concepts/storage/persistent-volumes/#persistent-volume-claim-requesting-a-raw-block-volume * https://kubernetes.io/docs/concepts/storage/persistent-volumes/#pod-specification-adding-raw-block-device-path-in-container
and others? I personally believe a nice way would be to create 1-page with a list of all these tasks, I am still a bit confused about approaching this issue though.
I don't have a strong view on whether that should be one page or several. @Rishit-dagli if you want to do it as one page I think that sounds fine - it's an improvement on what we have now.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
/remove-lifecycle rotten
Help on this issue is welcome.
This issue has not been updated in over 1 year, and should be re-triaged.
You can:
/triage accepted
(org members only)/close
For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/
/remove-triage accepted
This is a refactor request
What would you like to be added Create a new task page that contains the task-like content relating to snapshots, such as Create a PersistentVolumeClaim from a Volume Snapshot. It's OK to create more than one page if you need to.
You should not need to write new content or change the existing content.
Make sure that the concept page for PersistentVolume hyperlinks to any pages that you create as part of this work.
Why is this needed The concept page is plenty big, and the snapshot tasks are hard to isolate from the rest of the text. When readers want to perform specific tasks, it helps if there is page that walks through the steps to follow without diversions.
Comments Add the refactor label to any pull request this makes a change, or flag to your review that that label is needed. /language en
It's OK to address this issue through multiple pull requests. Mention me (@sftim) if you are working on this and would like help with the work - you can comment on this issue with your query. The wider Documentation SIG will also be available to offer tips.