Inside the Kubernetes connector: managed clusters and the in-cluster reader

Two ways in: AKS, EKS and GKE through the cloud provider's read-only API, or any cluster through a read-only ServiceAccount. Neither ever execs into a pod or reads a Secret.

There are two ways to connect a cluster, and you can use either or both.

1. Cluster posture (managed clusters)

2. Security configuration (managed clusters)

3. Inside the cluster (in-cluster reader, Beta)

The ServiceAccount can only get and list nodes, namespaces, pods, service accounts, resource quotas, deployments, statefulsets, daemonsets, ingresses, network policies, RBAC roles and bindings, cert-manager certificates, and Velero backups and schedules. From those we flag: a version past upstream end of life, nodes not ready or under pressure, kubelet version skew, unavailable workloads, CrashLoopBackOff and image-pull failures and high restart counts, :latest or untagged images, missing memory limits, privileged, host-namespace or hostPath workloads, namespaces with no NetworkPolicy, Ingresses without TLS, cert-manager certificates nearing expiry, cluster-admin bindings to non-system subjects, wildcard roles, a default service account that mounts its token, ResourceQuota usage at 80% and 95%, and Velero schedules with no recent completed backup.

The API server has to be reachable from the public internet over HTTPS, and TLS verification is always on. A private cluster cannot use this reader; if it is AKS, EKS or GKE it is still covered at the management-API level. An outbound-only agent for private clusters is built but not offered yet.

What the Kubernetes connector does NOT do

Clusters are scanned every hour: node readiness, workload availability and restart loops are exactly the kind of state that changes between one nightly pass and the next. An account administrator can ask for a fresh scan of a connection, at most once every 15 minutes per account; it runs with the next hourly scan, and while CloudMonitor is pre-launch nothing scans during the part of each day the service is powered down (see the Terms). The manifest and setup steps are on the Connectors page.

← Back to all posts