Set Up GKE Cluster
GCP-native.
Overview
GKE is Google’s managed Kubernetes. Two modes: Autopilot manages nodes, networking, and most cluster operations for a per-pod price; Standard gives full node control at the per-node price. The first cluster establishes the patterns: Workload Identity for pod auth, Terraform for cluster config, native GCP integration for load balancing and storage.
- GCP-native integration. Cloud IAM, Cloud Logging, Cloud Monitoring. Native auth and observability.
- Autopilot mode. Google manages nodes; per-pod billing. Right for small teams that want minimal operational surface.
- Standard mode. Full node control. Right when GPU pools or custom node OS matter.
- Workload Identity plus native GCP integration. Pod-to-IAM identity binding; Cloud Load Balancing, Filestore, Persistent Disk all integrate without glue.
The approach
Three habits make a first GKE cluster production-ready: Autopilot by default, Standard only when specific needs justify the operational cost, Workload Identity wired up so pods never see static credentials.
- Autopilot for most workloads. Reduces operational burden. Small teams ship faster.
- Standard for specific needs. GPU pools, custom node OS, specialised networking. The cases where Autopilot does not fit.
- Workload Identity. Pods bind to GCP service accounts. Static credentials disappear.
- Terraform-managed plus documented topology. Google provider creates GKE; per-cluster the configuration documented.
Why this compounds
Each cluster inherits the patterns established by the first. The team’s GCP Kubernetes fluency deepens; new clusters take days, not weeks; native GCP integrations like Workload Identity and Cloud Load Balancing fall into place naturally.
- Operational burden reduced. Google manages the substrate. Engineering time stays on workloads.
- GCP integration native. Auth, monitoring, networking integrate cleanly. Glue code shrinks.
- Reusable patterns. Standard Terraform modules capture conventions across clusters.
- Year-one investment, year-two habit. First cluster is heavy lift. By the third, the template is settled.