Google Cloud and Kubernetes are a common pairing in a modern DevOps stack. Here is how they fit together and a practical way to wire them up.
Where Google Cloud fits
Google Cloud offers compute (GCE, GKE, Cloud Run), storage (GCS), networking and managed data/AI services, with GKE as the reference Kubernetes experience and strong IAM.
resource "google_storage_bucket" "assets" {
name = "acme-assets"
location = "EU"
uniform_bucket_level_access = true
versioning { enabled = true }
}Where Kubernetes fits
Kubernetes is a container orchestrator: you declare the desired state of your workloads in YAML and controllers continuously reconcile the cluster toward it, handling scheduling, scaling, healing and networking.
apiVersion: apps/v1
kind: Deployment
metadata: { name: web }
spec:
replicas: 3
selector: { matchLabels: { app: web } }
template:
metadata: { labels: { app: web } }
spec:
containers:
- name: web
image: ghcr.io/acme/web:1.0
ports: [{ containerPort: 3000 }]
resources:
requests: { cpu: 100m, memory: 128Mi }
limits: { cpu: 500m, memory: 256Mi }
readinessProbe:
httpGet: { path: /healthz, port: 3000 }
---
apiVersion: v1
kind: Service
metadata: { name: web }
spec:
selector: { app: web }
ports: [{ port: 80, targetPort: 3000 }]Making them work together
- Use Workload Identity Federation - no exported SA keys
- Grant least-privilege predefined roles per service account
- Set requests/limits and use the HorizontalPodAutoscaler for elastic workloads
- Separate config (ConfigMap) from secrets and mount them, don't bake them in
Want this pairing set up properly, with docs and handover? That is exactly the kind of work CodeWizard's embedded senior engineers do - and both Google Cloud and Kubernetes have active community groups you can join for free.