CMK version:
2.3.0p30
OS version:
AlmaLinux 9.4
Error message:
Checkmk Kubernetes integration returns 404 on /pods and /nodes endpoints.
ClusterCollector metadata works fine using a valid ServiceAccount token, but /collector/pods and /collector/nodes return:
{
"detail": "Not Found"
}
The UI connects but shows no resources, pods, nothing, despite all settings activated.
Output of “cmk --debug -vvn hostname”: (If it is a problem with checks or plugins)
N/A – issue is with Kubernetes cluster integration, not a specific host/service.
Extra Context
I tried the Prometheus integration first, but got some error, and the forums suggested doing the kubernetes intregration instead. I followed the instructions.
The UI shows:
OK Cluster collector Cluster collector version: 1.7.0, Nodes with container collectors: 1/1, Nodes with machine collectors: 1/1, Container Metrics: OK, Machine Metrics: OK
OK CPU resources Requests: 0.000 (0/0 containers with requests), Limits: 0.000 (0/0 containers with limits), Allocatable: 0.000
OK Info Name: my.dns.address
OK Kubernetes API Live, Ready
OK Memory resources Requests: 0 B (0/0 containers with requests), Limits: 0 B (0/0 containers with limits), Allocatable: 0 B
OK Nodes Worker nodes 1/1, No control plane nodes found
OK Pod resources Running: 0, Pending: 0, Succeeded: 0, Failed: 0, Unknown: 0, Allocatable: 0
But there are pods running.
ServiceAccount and RBAC are working fine — /metadata works.
cat check_mk_values.yaml
global:
clusterName: my.dns.address
clusterCollector:
enabled: true
containerArgs:
- --log-level=warning
- --address=0.0.0.0
- --reader-whitelist=kube-system:checkmk-kube-agent-checkmk
service:
type: NodePort
port: 8080
nodePort: 31724
nodeCollectors:
enabled: true
I added these extra bits in, because metadata wasn’t accessible without the whitelist. The nodeCollectors doesn’t do anything.
Any help appreciated.