Build Cloud Run service revision configurations with autoscaling, VPC access, probes, and traffic splitting.
Last verified: May 2026
Build Cloud Run service revision configurations with autoscaling, VPC access, probes, and traffic splitting.
Required Fields
metadata.namespec.template.spec.containersspec.trafficOutput will appear here...Build Cloud Run service revision configurations with autoscaling, VPC access, probes, and traffic splitting. This tool helps GCP engineers generate valid configurations quickly without consulting documentation, reducing errors and accelerating infrastructure deployment. All processing runs in your browser with no data sent to external servers.
No. This tool runs entirely in your browser and generates configuration JSON that you can copy and paste into your infrastructure-as-code templates, CLI commands, or cloud console. It never connects to any cloud account or sends data externally.
The tool produces syntactically valid configurations based on current GCP service specifications. Always review generated configs against your organization security policies and test in a non-production environment before deploying.
Your team's Cloud Run service deploys are inconsistent — some have proper resource limits, some don't, environment variables are scattered across deployment scripts. The builder generates a canonical service.yaml: 256 MB memory, 1 vCPU, concurrency 80, min-instances=1 for prod / 0 for staging, secrets from Secret Manager via Cloud Run secret references, VPC connector for accessing Cloud SQL via Private Service Access, startup probe on /healthz. The same template (with parameterized env values) deploys consistently across staging and prod. Drift between environments eliminated.
The builder constructs Cloud Run service configurations: service resource with template (container image, command, env vars, secret references, resource limits, concurrency, timeout, VPC connector, service account, startup/liveness probes), traffic split (between revisions for canary/rollback), labels and annotations, ingress (all/internal-and-cloud-load-balancing/internal). Output is generated as gcloud run services replace YAML and Terraform google_cloud_run_v2_service resources.
Cloud Run revision configurations are immutable — each deploy creates a new revision, traffic is split between revisions via the service's traffic config. This enables instant rollback (just shift traffic back to the previous revision) and canary deploys (route 5% to new revision, monitor, promote).
Always set min-instances=1 for user-facing production services. The cost (~$15-20/month per always-on instance) is dramatically less than the UX impact of cold starts on first user request. For internal services and webhook handlers, min-instances=0 (true scale-to-zero) is fine.
Concurrency setting (default 80) is the single biggest performance lever. CPU-bound work: lower (10-20) so each instance has CPU resources. I/O-bound work: keep at 80 or raise to 200+ for maximum efficiency. Profile your real workload before tuning.
Was this tool helpful?
Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.