Skip to main content

GCP Container Node Pool

A GCP (Google Cloud Platform) Container Node Pool is a logical group of identical Compute Engine virtual machines that run as worker nodes within a Google Kubernetes Engine (GKE) cluster. Each pool may have its own machine type, disk settings, metadata, autoscaling rules and upgrade channel, allowing you to tailor subsets of the cluster to different workloads or cost profiles. Official documentation: https://cloud.google.com/kubernetes-engine/docs/concepts/node-pools

Terrafrom Mappings:

  • google_container_node_pool.id

Supported Methods​

  • GET: Get a gcp-container-node-pool by its "locations|clusters|nodePools"
  • LIST
  • SEARCH: Search GKE Node Pools within a cluster. Use "[location]|[cluster]" or the full resource name supported by Terraform mappings: "[project]/[location]/[cluster]/[node_pool_name]"

gcp-compute-node-group​

Every GKE node pool is implemented under the hood as a managed instance group (node group). Linking to the corresponding gcp-compute-node-group lets you inspect the actual VM instances, autoscaling configuration and health information that back the node pool.

gcp-cloud-kms-crypto-key​

If the node pool is configured to use Customer-Managed Encryption Keys (CMEK), the boot disks of all nodes are encrypted with a specific KMS crypto key. Following this link allows you to verify key rotation policies and access controls that protect the node disks.

gcp-iam-service-account​

Each node in the pool runs with a Google service account that grants it permissions to pull images, write logs, and access other Google APIs. Linking to the related gcp-iam-service-account helps you audit the IAM roles and trust relationships associated with the node pool.