What's changed: Created Professional Cloud Developer Chapter 4 (Domain 3 "Configuring for deployment": deploy to Cloud Run = source deploy/revisions/traffic splitting/Eventarc-Pub/Sub triggers/Apigee; deploy to GKE = Deployment/Service, liveness/readiness probes, Horizontal Pod Autoscaler, Cloud Run vs GKE).
4.2Deploying to GKE
Understand deploying containerized apps to GKE (Deployments, Services), Kubernetes health checks (liveness/readiness probes) for availability, scaling with the Horizontal Pod Autoscaler, and choosing between Cloud Run and GKE.
For finer control or complex orchestration, deploy to GKE (Kubernetes). Ensure availability and scalability via Kubernetes mechanisms.
4.2.1Deploying and health checks
Place containerized apps with a Deployment (declare desired Pod count) and expose them via a Service. For availability, set health checks (liveness probe = restart on failure; readiness probe = do not send traffic until ready). This prevents requests reaching Pods that are starting or unhealthy. Map "restart on failure = liveness" and "no traffic until ready = readiness."
4.2.2Scaling and choosing
To scale Pod count with load, use the Horizontal Pod Autoscaler (HPA), scaling on CPU utilization or custom metrics. Choose between Cloud Run and GKE by: "serverless, minimal ops = Cloud Run" and "fine control, complex orchestration, existing Kubernetes = GKE." Map "scale Pods by load = HPA" and "minimal ops = Cloud Run, fine control = GKE."
Continue reading — free sign-up
You're reading the free preview. Sign up free to read this section in full, plus every chapter (including 4+) and all questions.