Ctadel

Kubernetes module

The Kubernetes page is the topology view of your clusters, distinct from the KSPM page (which is rule-based).

Tabs

Clusters

Lists every connected cluster.

ColumnNotes
NameCluster identifier.
CloudProvider logo. EKS / AKS / GKE / Kapsule / self-hosted.
RegionWhen applicable.
VersionKubernetes minor version.
NodesCount of nodes.
PodsCount of running pods.
IssuesTotal count of OPEN findings (KSPM + IaC + secrets in cluster + CVEs in pods).
PublicBullet if the API server is internet-reachable.
CNIThe CNI plugin in use (calico, cilium, etc.).
Statushealthy, degraded.

Clicking a cluster opens its detail panel with cluster-level configuration, the network topology summary, and a graph slice.

Nodes

Lists every node across every cluster.

ColumnNotes
NodeHostname.
ClusterWhich cluster the node belongs to.
Cloud / RegionThe underlying VM.
Kubelet versionDetected from the node status.
StatusReady, NotReady.
PodsCount of pods scheduled on this node.
OSLinux distro + kernel.

Useful for correlating an HCR finding (CIS-K8S-4.2.6) back to the specific node.

Workloads

Lists every Deployment, StatefulSet, DaemonSet, Job, CronJob.

ColumnNotes
NameWorkload name.
Cluster / NamespaceWhere the workload runs.
KindDeployment / StatefulSet / etc.
CloudProvider logo.
ReplicasDesired / available.
IssuesOPEN finding count (KSPM + image CVEs).

Clicking a workload opens its detail panel with the spec excerpt and any associated findings.

Filters

Each tab has cloud + region filters, plus a free-text name search.

Tips

  • Public API + Issues > 0 is your priority list. Filter clusters by Public: yes and sort by issues.
  • Workloads with no replicas are dormant deployments worth removing, as they often carry old image CVEs.
  • Nodes view is the bridge to HCR. A KSPM finding on a Pod can often be traced down to a host-level CIS finding on the underlying node.

What's next