Werk #22179: Kubernetes: agent_kube special agent deprecation
| Component | Checks & agents | ||
| Title | Kubernetes: agent_kube special agent deprecation | ||
| Date | Sep 12, 2026 | ||
| Level | Prominent Change | ||
| Class | New Feature | ||
| Compatibility | Incompatible - Manual interaction might be required | ||
| Checkmk versions & editions |
|
The Kubernetes special agent (agent_kube) is being deprecated and will be
replaced by a new in-cluster agent. The cluster collector and node collectors
(checkmk_kube_agent) are deprecated along with it.
The "Kubernetes" rule set for configuring agent_kube will also be deprecated. It will now have the "Deprecated" label in the UI and can be found under "Deprecated Rule Sets" in the Setup menu. A new rule set with the same name will replace it and can be used to configure the new Kubernetes special agent, which will pull data from your cluster.
Note that in Checkmk 3.0, your old agent_kube special agent rule will continue
working but you will not be able to create a new one. In Checkmk 3.1, the
agent_kube special agent is planned for removal entirely.
Additionally, the option to source usage data from OpenShift's Prometheus/Thanos
is being dropped in favor of the new in-cluster agent, which will support
OpenShift. Users who still wish to query OpenShift's Prometheus directly in
Checkmk 3.0 can use the Prometheus special agent (agent_prometheus) with it.
Details about the new Kubernetes monitoring capabilities in Checkmk 3.0 will follow in future werks.