CatherineF-dev
CatherineF-dev
/ok-to-test
I think semantic commit message is better. If someone forgot to update changelog, we need to manually go through all changes again.
/remove-lifecycle stale
/close It's in 1.29.0 already
Could you curl kube-state-metrics endpoint to get full metrics payload? For example, ```bash # change kube-system to correct namespace where kube-state-metrics exists kubectl -n kube-system port-forward pod/kube-state-metrics-xxx 9443:9443 curl http://localhost:9443/metrics...
Could you list pods which are in failed or pending status? Also list the reasons. It might be because current implementations only include these three reasons {NodeLost, Evicted, UnexpectedAdmissionError}.
fyi: Pod metrics are implemented in this file https://github.com/kubernetes/kube-state-metrics/blob/main/internal/store/pod.go You can have a look at this file to figure out what happened. I am curious on whether kube_pod_status_reason didn't reports...
I found the reason. It's because using bounded reasons. ``` podStatusReasons = []string{"Evicted", "NodeAffinity", "NodeLost", "Shutdown", "UnexpectedAdmissionError"} ``` https://github.com/kubernetes/kube-state-metrics/blob/main/internal/store/pod.go#L40
Could you try updating https://github.com/kubernetes/kube-state-metrics/blob/main/internal/store/pod.go and rebuilding a new kube-state-metrics? Wondering what's the reason for `Back-off pulling image "harbor.hulk.beast-code.com/phactory-images/cleanup-deploy:master"`
Or could you run `kubectl -n deploy get pod clean-deploy-cronjob-28152630-jzrsj -o yaml`