-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Add "Terminating" status in kube_persistentvolumeclaim_status_phase metrics #1437
Comments
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
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:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close |
@k8s-triage-robot: 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. |
@roystchiang are you still interested in this issue and should we reopen it? |
What would you like to be added:
I would like to see which PVCs are in
Terminating
state in thekube_persistentvolumeclaim_status_phase
metricWhy is this needed:
This will be useful to see how many PVCs are stuck or accidentally deleted. Right now, PVCs are either
Bound
,Lost
, orPending
. If a PVC is inTerminating
state because a pod is still using it, it will show up asBound
.Describe the solution you'd like
Similar to #1013, we could expose the
Terminating
stateAdditional context
The text was updated successfully, but these errors were encountered: