Skip to main content
One parallel call across a fleet of clusters producing a comparison matrix that flags the cluster whose Kubernetes version, image, and CRD count have drifted
When managing multiple clusters, drift happens: different Kubernetes versions, mismatched images, inconsistent configurations. An agent can audit all clusters in parallel, comparing everything from node versions to installed CRDs.

Version drift check

An agent asked “are my clusters running the same versions?” fans out across all clusters in a single execute call:

Image consistency

Compare which container images are running across clusters, catching cases where one cluster is on v1.2.3 and another is still on v1.1.0:

CRD comparison

Check which Custom Resource Definitions are installed in each cluster, useful for ensuring all clusters have the same operators and extensions:

Why this matters

Multi-cluster management typically requires dedicated tools (fleet managers, policy engines, GitOps controllers). For ad-hoc checks and audits, Code Mode gives agents the same cross-cluster visibility without any additional infrastructure. The agent uses the Akua API to list clusters, then fans out through each cluster’s kube proxy in parallel. It composes the comparison logic (version matching, image diffing, CRD set intersection) inside the sandbox. One conversation, full fleet visibility.

CRD discovery

Discover and interact with custom resources on a single cluster.

Security audit

Audit pod security, RBAC, and network policies in one call.

Kubernetes access

The kube proxy endpoints agents use for cluster inspection.

Code Mode in action

How the parallel fan-out pattern works.