Pod readiness metrics, part 2 #2250
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
What would you like to be added:
I would like kube-state-metrics to be able to report on pod readiness gates in order to have proper alerting set up for readiness gates which are not proceeding.
Why is this needed:
This is to be able to monitor and alert on stuck readiness gates from within the viewpoint of Kubernetes.
This issue was originally raised in #1981 with a proposed solution (combining it into the overall pod ready status), but was closed because that solution was deemed not satisfactory. I propose an alternative solution below.
Describe the solution you'd like
I propose the creation of two new metrics, tentatively named
kube_pod_readiness_gate_status_total
andkube_pod_readiness_gate_status_ready
, to track the number of total PRGs and the ready number thereof.The disposition of these metrics can be determined fairly simply by inspecting the pod spec and status (examples taken below from a real pod):
For a given pod, the total metric would be determined by the number of entries in the spec.readinessGates array, and the number of ready PRGs would be determined by following each entry from the array to the matching conditions of that type in status.conditions and seeing which ones are reporting
status: "True"
.Additional context
I am happy to do the work to implement this, I just want a thumbs up on the proposed methodology before I do anything.
The text was updated successfully, but these errors were encountered: