I also got the same status code 404 when using the K8s Agent with the following versions:
docker image = checkmk/check-mk-raw:2.0.0p17
kubernetes = 1.22.5
The error on the UI is the following:
Agent exited with code 1: (404)
Reason: Not Found
HTTP response headers: HTTPHeaderDict({‘Audit-Id’: ‘745831d9-0307-448c-9a94-cf4b31dca388’, ‘Cache-Control’: ‘no-cache, private’, ‘Content-Type’: ‘text/plain; charset=utf-8’, ‘X-Content-Type-Options’: ‘nosniff’, ‘X-Kubernetes-Pf-Flowschema-Uid’: ‘a5702eaf-86a4-44e6-9156-623ccd9297b1’, ‘X-Kubernetes-Pf-Prioritylevel-Uid’: ‘3c611a5c-dfc2-4112-94d1-295497ebe9de’, ‘Date’: ‘Wed, 16 Mar 2022 14:18:38 GMT’, ‘Content-Length’: ‘19’})
HTTP response body: 404 page not found
When redeploying the sameK8s cluster but with version 1.21.5 it worked fine.
I also tested with different versions of checkmk which I got the following errors:
-
2.0.0p21 - Gets the same error
-
2.1.0b2 - Get error “Agent exited with code 1: ‘NoneType’ object has no attribute ‘partition’”
Kubernetes only maintains release branches for the most recent three minor releases which currently are 1.23, 1.22 and 1.21.
I’m wondering if checkmk can keep the pace and be always compatible with at least one of the last 3 K8s minor versions ( Releases | Kubernetes), because this is a most for a production environment. Is this something that can be guaranteed by checkmk?