Plan improvements to Storage concepts

[sftim]

This is a Feature Request

What would you like to be added?

The work to do here is unusual. Rather than making pull requests, your first job is to make some more issues, about improvements to how we explain Kubernetes storage management.

This issue is done when we have a set of issues opened that describe a series of approachable issues that each propose a useful improvement to storage concepts.

Aim to plan out the set of issues so that they are mostly settled before opening the first of those approachable, single-improvement-at-a-time issues.

Why is this needed

The existing storage pages are not easy to understand, and the issues we have open are not very approachable. We might:

• migrate some content to a tutorial page
• combine pages
• decide that we need to make a new task page
• define some reference pages, and open an issue for each reference page that needs adding
• add text into https://kubernetes.io/docs/concepts/storage/ (it is purely autogenerated at the time of writing)

:information_source: try not to directly work on PRs for this issue; instead, start on making a complete set of storage-related issues, close this one off because it is done, and then work on each issue on turn.

It is OK to make an umbrella issue to act as a successor for this issue.

Selected existing pages

• Volumes
• Persistent Volumes
• Dynamic Volume Provisioning
• Storage Classes

and associated tasks (in case we want to link to them):

• Limit Storage Consumption
• Configure a Pod to Use a PersistentVolume for Storage
• Configure a Pod to Use a Volume for Storage
• Change the Access Mode of a PersistentVolume to ReadWriteOncePod
• Configure a Pod to Use a Projected Volume for Storage

[sftim]

/triage accepted /lifecycle frozen /priority important-longterm

[sftim]

Also see:

• https://github.com/kubernetes/website/issues/31159
• https://github.com/kubernetes/website/issues/43293

[network-charles]

I'm glad you brought this issue up, @sftim. I struggled through the docs while learning about storage concepts. For example, while attempting to provision a static local persistent volume, hence binding my persistent volume claim to my persistent volume, the docs only mentioned using a selector for binding, but they didn't explicitly specify that a volumeName could also be used. Plus, no proper example exists for each access mode. It will be nice to add one to the new task page. You could assign it to me if you think these few suggestions make sense.

Summary

1. Add an example on the new task page titled "Configure a Pod to Use a Static Local Persistent Volume and ReadWriteOnce Access Mode"
2. Add a subsection under "PersistentVolumeClaims" titled volumeName since it exists on the reference page.