Improve Volumes concept page (including diagram?)

[JoeKuan]

For beginners with little knowledge of k8, the Volumes should just give a very general picture of managing storage, instead the concept page gives a long list of different type of volumes which most beginners don't really need at this point.

The PV in Static and Dynamic provisioning should be presented with a diagram to illustrate the significance and how different are them.

Basically, I have to rely on external sources to understand volumes in k8 rather than the concept page. IMHO, when it comes to concept, always pictures than words.

[sftim]

/sig storage

[Kartik494]

For beginners with little knowledge of k8, the Volumes should just give a very general picture of managing storage, instead the concept page gives a long list of different type of volumes which most beginners don't really need at this point.

Hi @JoeKuan Could you please elaborate how do you want to implement this part ? I think added some description would be great? is anyone working on this issue

[k8s-triage-robot]

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:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[Kartik494]

/remove-lifecycle stale

[k8s-triage-robot]

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:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

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:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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.

[network-charles]

@sftim, I'd like to work on this issue. Let me know what you think about my suggestions.

From the below comment, the volume page indeed lacks an introduction to what a volume is. Instead, it went ahead and talked about the problem a volume solves.
I can add a brief introduction to what a volume is.

For beginners with little knowledge of k8, the Volumes should just give a very general picture of managing storage, instead the concept page gives a long list of different type of volumes which most beginners don't really need at this point.
Page: https://kubernetes.io/docs/concepts/storage/volumes/

I'd also like to ask a question about another comment from the contributor who opened the issue.

The PV in Static and Dynamic provisioning should be presented with a diagram to illustrate the significance and how different are them.
Page: https://kubernetes.io/docs/concepts/storage/persistent-volumes/

I'm not sure how I should represent the diagram, as per the diagram guide. Below is a rough sketch of what I plan to do.

[sftim]

We can't plagiarize the diagram in https://medium.com/devops-mojo/kubernetes-storage-options-overview-persistent-volumes-pv-claims-pvc-and-storageclass-sc-k8s-storage-df71ca0fccc3 but that is more the kind of thing I'd expect to see.

PS this issue is marked as Closed. Do you want it reopened @network-charles ?

[network-charles]

Yes, I’d like it reopened.

Ah, I have a similar diagram to that here. You are referring to something like that, right?

[sftim]

/reopen

/retitle Improve Volumes concept page (including diagram?)

[k8s-ci-robot]

@sftim: Reopened this issue.

In response to this:

/reopen

/retitle Improve Volumes concept page (including diagram?)

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-sigs/prow repository.

[sftim]

/language en
/remove-lifecycle rotten
/triage accepted
/priority backlog

[network-charles]

@sftim, what do you think about these new diagrams for the static and dynamic volumes?

[sftim]

[I'm happy to let anyone do review here]

[sftim]

/uncc

[network-charles]

Alright

[sftim]

See #49154

[sftim]

Closing in favor of #49419

[sftim]

/close

[k8s-ci-robot]

@sftim: Closing this issue.

In response to this:

/close

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-sigs/prow repository.

[sftim]

Oops.
/reopen

[k8s-ci-robot]

@sftim: Reopened this issue.

In response to this:

Oops.
/reopen

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-sigs/prow repository.

[sftim]

/close not-planned

[k8s-ci-robot]

@sftim: Closing this issue, marking it as "Not Planned".

In response to this:

/close not-planned

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-sigs/prow repository.