What problem does it solve? Deploying services to Google Cloud Run involves many error-prone steps: building multi-stage container images, pushing to Artifact Registry, configuring IAM, autoscaling, and ingress rules. This Skill standardizes the entire procedure so deployments follow a consistent, least-privilege, declarative workflow instead of ad-hoc CLI commands. ## Core Features & Use Cases - Container Build & Push: Builds multi-stage Docker images via Google Cloud Build and pushes them to Google Artifact Registry. - Declarative Deployment: Deploys services using a Knative CloudRunService.yaml manifest with autoscaling, resource limits, probes, and service account configuration, or via direct gcloud run deploy commands. - IAM & Ingress Control: Configures roles/run.invoker bindings to restrict internal services to specific service accounts or expose public frontends to allUsers. - Use Case: A backend service needs to go live in europe-west2 with min 1 / max 10 instances, 80 concurrency, and no unauthenticated access. Follow the SOP to build the image, apply the YAML manifest, and verify health with a curl liveness check. ## Quick Start Deploy my backend service to Cloud Run in europe-west2 using the declarative Knative manifest and restrict access to the orchestrator service account.
