jgagnon44

Just discovered that the kube-state-metrics pod is running in the lens-metrics namespace. Not sure what that means. Was expecting to see it in the namespace you mentioned. In any case,...

This is interesting. If I query this metric in Prometheus, I get 5 result entries per pod. If I port forward and access the kube-state-metrics /metrics, I'm only getting 3...

Here are the current failed or pending pods on the cluster: | Pod | Namespace | Status | Reason | | --- | --- | --- | --- | |...

Is it possible to reconfigure this to be non constrained?

I'm guessing this is unrelated. In any case: ``` containerStatuses: - image: harbor.hulk.beast-code.com/phactory-images/cleanup-deploy:master imageID: "" lastState: {} name: clean-deploy ready: false restartCount: 0 started: false state: waiting: message: Back-off pulling...

Not sure how to attempt what you suggest RE updating the .go file and rebuilding. Also, I don't know Go and am not sure what can be done to make...

Both containers in that pod show: ``` state: terminated: exitCode: 137 finishedAt: null message: The container could not be located when the pod was terminated reason: ContainerStatusUnknown startedAt: null ```...

I'm curious about the fact that the kube-state-metrics pod is deployed in the lens-metrics namespace instead of kube-system. This is the only instance of a pod with this name that...

> Could you see these pods in metric kube_pod_status_phase? Yes. runner-goew1uzh-project-8-concurrent-0zk79h and runner-goew1uzh-project-8-concurrent-1fhtb4 show phase=Failed clean-deploy-cronjob-28151190-fqqgs and clean-deploy-cronjob-28152630-jzrsj show phase=Pending

kube_pod_status_phase is only showing five statuses: Failed, Pending, Running, Succeeded and Unknown, with a value of 1 for each pod that is in a particular status. E.g.: Query: kube_pod_status_phase{pod="runner-goew1uzh-project-8-concurrent-1fhtb4"} Result:...