Getting error: no unmonitored services found, no vanished services found [special_kubernetes] Agent exited with code 1: (404)

Hi Sudhir,

Thanks for update, let me try to deploy and configure using checkmk version 2.1.0…

Nitin Goyal

1 Like

I’m facing the same problem since updating a Kubernetes cluster to 1.22.
Digging into the issue it seems as if the problem arises when the special agent wants to access “/apis/extensions/v1beta1/ingresses”. Doing the same with curl results in

curl -X GET "https://<api-server>/apis/extensions/v1beta1/ingresses" --header "Authorization: Bearer $TOKEN" --insecure
  "kind": "Status",
  "apiVersion": "v1",
  "metadata": {

  "status": "Failure",
  "message": "ingresses.extensions is forbidden: User \"system:serviceaccount:check-mk:default\" cannot list resource \"ingresses\" in API group \"extensions\" at the cluster scope
  "reason": "Forbidden",
  "details": {
    "group": "extensions",
    "kind": "ingresses"
  "code": 403

I.e. it must be assumed that the API changed starting with version 1.22 (1.21 works fine).

This problem has been fixed in 2.1