Setting the file. One moment. 10.8
Cloudrun Assessment Guide
- CPU/Memory: Cloud Run (1–4 vCPU, 128 MiB–32 GiB) → Container Apps (0.25–4 vCPU, 0.5–8 Gi)
- Images: Registry location (GCR or Artifact Registry), image size, base image
- Port: Exposed port (Cloud Run default 8080)
- Environment Variables: Static values, secret references, service URLs
- Concurrency: Per instance (default 80, max 1000) → Container Apps (1–300)
- Min/Max Instances: 0–1000 → Container Apps 0–300 per revision
- Timeout: Max 60 min → Container Apps max 30 min (1800s)
- CPU Allocation: Request-based vs always → Container Apps always allocated
- HTTP/2, WebSockets, gRPC: Document if used
- Ingress: Public, internal (VPC), or internal + load balancing
- Custom Domains: List domains and SSL certificates
- VPC Connector: Region, IP range, connected VPC
- Dependencies: Cloud SQL, Firestore, Cloud Storage, Pub/Sub, Redis, external APIs
- Service Account: Default or custom
- IAM Roles: Storage, Firestore, Pub/Sub, Secret Manager, Cloud SQL permissions
- Task role policies → Managed Identity + Azure RBAC
- Secret Manager access → Key Vault RBAC (recommended) or access policies for vaults still using access-policy mode
- Logging: Destinations, structured logs (JSON)
- Monitoring: Request metrics, CPU/memory, instance count
- Tracing: Cloud Trace → Application Insights
- Eventarc: Pub/Sub triggers, Cloud Storage triggers
- Cloud Scheduler: Schedule (cron), target endpoint
- Cloud Run: Request charges, CPU/memory time
- Data transfer egress charges
- Container Registry storage
- Low: Single container, public ingress, standard env vars, no VPC
- Medium: Internal ingress, Pub/Sub triggers, custom service account, Cloud Scheduler
- High: Complex traffic management, VPC networking, multiple Eventarc triggers, long-running requests (>30 min)
references/services/container-apps/cloudrun-assessment-guide.md