Most Kubernetes monitoring tools ask you to deploy an in-cluster operator — its own Deployment, its own RBAC bindings, its own upgrade cycle, separate from the rest of your monitoring stack. Kllyroo takes a different, deliberately simpler approach: the same agent already running on a host with cluster access uses kubectl to poll node, pod, and deployment status on its normal check-in cycle, then reports it through the exact same protocol it already uses for host and container data.
That's a real trade-off, stated plainly: detection cadence follows the agent's check-in interval rather than a live watch stream, and there's no continuous in-cluster event tail. What you get in exchange is one thing to install instead of two, and Kubernetes data sitting in the same dashboard as everything else — not a separate tool with a separate login.