Skip to content
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

Explain in context the kind of principal making a (persistent) volume claim #23902

Closed
guettli opened this issue Sep 15, 2020 · 7 comments
Closed
Labels
kind/feature Categorizes issue or PR as related to a new feature. language/en Issues or PRs related to English language lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/storage Categorizes an issue or PR as relevant to SIG Storage.

Comments

@guettli
Copy link
Contributor

guettli commented Sep 15, 2020

On this page: https://kubernetes.io/docs/concepts/storage/persistent-volumes/

A PersistentVolumeClaim (PVC) is a request for storage by a user.

It would be very nice if user would be a hyperlink to a definition/documentation about what a user is for you in this context.

@sftim
Copy link
Contributor

sftim commented Sep 15, 2020

Possible fix: add “user” to the glossary, reference that definition here.

The page could also explain what this means for organizations that separate development and IT operations into separate activities; in those cases, the IT operations team need to ensure that the storage is available for claiming.

Documentation is owned by
/sig storage

@k8s-ci-robot k8s-ci-robot added the sig/storage Categorizes an issue or PR as relevant to SIG Storage. label Sep 15, 2020
@guettli
Copy link
Contributor Author

guettli commented Oct 1, 2020

@sftim thank you for looking at this. There is no progress since some days. How to contact sig/storage?

@sftim
Copy link
Contributor

sftim commented Oct 1, 2020

@guettli the vast majority of contributors are volunteers. If you wanted to pay for someone to work on it then there are certainly firms who'll take your money. Otherwise, it's on the backlog of improvements that people could pick up.

/priority backlog
/language en
/kind feature

What I will do is retitle this to try to explain what work is required.
/retitle Explain in context the kind of principal making a (persistent) volume claim

@k8s-ci-robot k8s-ci-robot added the priority/backlog Higher priority than priority/awaiting-more-evidence. label Oct 1, 2020
@k8s-ci-robot k8s-ci-robot changed the title Persistent Volumes Explain in context the kind of principal making a (persistent) volume claim Oct 1, 2020
@k8s-ci-robot k8s-ci-robot added language/en Issues or PRs related to English language kind/feature Categorizes issue or PR as related to a new feature. labels Oct 1, 2020
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 30, 2020
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 29, 2021
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/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/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. language/en Issues or PRs related to English language lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/storage Categorizes an issue or PR as relevant to SIG Storage.
Projects
None yet
Development

No branches or pull requests

4 participants