Document `kubernetes.io/limit-ranger` annotation on PersistentVolumeClaims (?)

[sftim]

This is a Bug Report

Problem: https://github.com/kubernetes/website/pull/34939/files#r991220411 commented on whether the kubernetes.io/limit-ranger annotation might get used on a PersistentVolumeClaim. It looks like it might be.

This issue is calling for action to determine what SIG Docs should document in terms of that annotation as applied specifically to PersistentVolumeClaims, and then to make any necessary changes.

Additional Information: /language en

[bishal7679]

/triage accepted

[kundan2707]

/assign

[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

[kundan2707]

/remove-lifecycle stale

[k8s-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

[kundan2707]

/triage accepted