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.1Deploying to Cloud Run
Understand deploying to Cloud Run from source, rollouts via revisions and traffic splitting, configuring triggers (Eventarc, Pub/Sub) and event receivers, and versioning/exposing/securing APIs with Apigee.
Cloud Run, which runs containers serverless, is a central deployment target for developers. Deploy easily from source and roll out safely.
4.1.1Deploying and rolling out
Cloud Run can deploy directly from source (auto-containerized internally). Each deploy creates a revision; traffic splitting enables canary (gradually shifting percentage to a new revision) and instant rollback on issues. Configure concurrency, CPU/memory, and min/max instances to tune performance and cost. Map "gradual rollout/rollback = revisions + traffic splitting."
4.1.2Triggers and exposing APIs
Cloud Run services can be invoked by Eventarc or Pub/Sub triggers to build event-driven processing (configure Eventarc/Pub/Sub as event receivers). Expose APIs with versioning, publishing, auth, rate limiting, and protection via Apigee. Map "invoke by events = Eventarc/Pub/Sub triggers" and "API versioning/protection = Apigee."
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.