Skip to main content

Managed Kubernetes

Integrate managed Kubernetes (EKS, AKS, GKE) with Cloudaware to inventory clusters and workloads for unified reporting. Cloudaware discovers cloud-provider metadata through the corresponding cloud integration and maps Kubernetes resources into the CMDB.

info
  • Audience: Cloudaware administrators, platform engineers
  • Outcome: Managed cloud Kubernetes clusters, such as Amazon EKS, Azure AKS, and Google GKE, are connected to Cloudaware and cluster/workload objects are continuously discovered in the CMDB

Capabilities​

The integration supports:

  • Read-only discovery of EKS, AKS, GKE resources (namespaces, nodes, pods, services, RBAC)
  • Workload correlation with Applications and related cluster assets
  • Search, reporting, and coverage analysis for managed Kubernetes objects

Prerequisites​

Before you begin, make sure you have:

  • Access to a Cloudaware account.
  • A user with access to the Admin Console and permissions to manage cloud accounts, organizations, and integrations (Cloudaware Administrator).
  • Permissions to create roles/assign permissions in the cluster in question.
  • Ensure that:
    • For EKS:
      • Cloudaware IAM role/user configured for AWS and mapped into the EKS cluster (access entries or aws-auth) with read‑only Kubernetes RBAC.
    • For AKS:
      • Cloudaware app registration with reader‑level Azure RBAC and required Graph/API permissions.
      • For Microsoft Entra/AD‑enabled AKS clusters: additional Kubernetes RBAC via a read‑only ClusterRole/ClusterRoleBinding.
    • For GKE: Cloudaware Google Cloud service account with least‑privilege access to the project (for example, Viewer) and Kubernetes Engine API enabled, plus cluster‑level read‑only Kubernetes RBAC.
    • For all clusters: Breeze is configured, with TunHub for connectivity.

Configuration​

At a high level:

  1. Ensure provider‑specific access is configured (see cloud provider guides).
  2. In Cloudaware, add the managed Kubernetes integration (see the cluster access guides for EKS, AKS, and GKE).
  3. For private clusters, deploy Breeze Agent with TunHub connectivity. See also: Private Kubernetes.