Skip to main content

GCP Container Cluster

Google Kubernetes Engine (GKE) container clusters are managed Kubernetes control-planes hosted on Google Cloud. A cluster groups together the control-plane and one or more node pools on which users schedule their containerised workloads. GKE adds opinionated defaults and managed features such as automatic upgrades, node‐auto-provisioning and built-in observability.
Official documentation: https://cloud.google.com/kubernetes-engine/docs/reference/rest/v1/projects.locations.clusters#Cluster

Terrafrom Mappings:

  • google_container_cluster.id

Supported Methods​

  • GET: Get a gcp-container-cluster by its "locations|clusters"
  • LIST
  • SEARCH: Search for GKE clusters in a location. Use the format "location" or the full resource name supported for terraform mappings.

gcp-cloud-kms-crypto-key​

A cluster may reference a Cloud KMS CryptoKey when customer-managed encryption is enabled for etcd (Secrets) or persistent disk encryption. Overmind links the cluster to the key that protects its data at rest.

gcp-compute-node-group​

If a node pool is configured to run on sole-tenant nodes, the cluster will be associated with one or more Compute Node Groups. This link shows which tenant groups back the worker nodes.

gcp-compute-network​

Every cluster is created inside a VPC network; its control-plane and node IP ranges live within that network (and associated subnets). The link reveals the VPC that provides connectivity for the cluster.

gcp-iam-service-account​

Clusters use service accounts for node instances, workload identity, and control-plane components. Overmind surfaces the service accounts that the cluster depends on for permissions.

gcp-pub-sub-topic​

Operational and audit logs from the cluster can be routed to Pub/Sub topics, and Notification Channels for cluster events can also target Pub/Sub. The link highlights the topics receiving messages originating from this cluster.