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
Comments
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 |
@sftim thank you for looking at this. There is no progress since some days. How to contact sig/storage? |
@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 What I will do is retitle this to try to explain what work is required. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-contributor-experience at kubernetes/community. |
@fejta-bot: Closing this issue. 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. |
On this page: https://kubernetes.io/docs/concepts/storage/persistent-volumes/
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.
The text was updated successfully, but these errors were encountered: