I have this prometheus pod , which is stuck in “CrashLoopBackOff” error from a long time. I have deployed this prometheus on kubernetes using helm charts through terraform.
Here are the logs for the pod:
level=error ts=2024-07-26T09:38:42.475741645Z caller=runutil.go:100 msg="function failed. Retrying in next tick" err="trigger reload: reload request failed: Post "http://127.0.0.1:9090/-/reload": dial tcp 127.0.0.1:9090: connect: connection refused" level=error ts=2024-07-26T09:38:47.476574611Z caller=runutil.go:100 msg="function failed. Retrying in next tick" err="trigger reload: reload request failed: Post "http://127.0.0.1:9090/-/reload": dial tcp 127.0.0.1:9090: connect: connection refused" level=error ts=2024-07-26T09:38:52.475724576Z caller=runutil.go:100 msg="function failed. Retrying in next tick" err="trigger reload: reload request failed: Post "http://127.0.0.1:9090/-/reload": dial tcp 127.0.0.1:9090: connect: connection refused" level=error ts=2024-07-26T09:38:57.475677836Z caller=runutil.go:100 msg="function failed. Retrying in next tick" err="trigger reload: reload request failed: Post "http://127.0.0.1:9090/-/reload": dial tcp 127.0.0.1:9090: connect: connection refused"
Here I have described the pod:
Pod described
I looked up for the resources requests and limits, PV and PVCs but nothing seemed to work.
1