The Kubernetes monitor status can remain as online, even when the cluster is unavailable

[bec-callow-oct]

Severity

Non-blocking

Version

Earliest tried was 2026.1.11492

Latest Version

I could reproduce the problem in the latest build

What happened?

The Kubernetes monitor does not have its own health check. Health checks are run as part of the deployment target health check. When these health checks fail such as when the cluster is unavailable, the monitor health check fails to execute. This causes the monitor status to become outdated since the the previous value will still be displayed.

Reproduction

1. Create a Kubernetes agent deployment target with the monitor enabled
2. Run the deployment target health check
3. Verify that the monitor status is Online
4. Disable the cluster (when testing locally with minikube use minikube stop) *
5. Re-run the deployment target health check. The health check should fail
6. Check the monitor status to see that it remains Online even though the cluster was unavailable

• Use minikube start to bring the cluster back online

Error and Stacktrace

More Information

No response

Workaround

No response