Loading source
Pulling the file list, source metadata, and syntax-aware rendering for this listing.
Source from repo
Assess and migrate workloads from AWS, GCP, or other clouds to Azure services.
Files
Skill
Size
Entrypoint
Format
Open file
Syntax-highlighted preview of this file as included in the skill package.
references/services/container-apps/cloudrun-assessment-guide.md
1# Assessment: Cloud Run to Container Apps23## Checklist45### 1. Service Configuration6- **CPU/Memory**: Cloud Run (1–4 vCPU, 128 MiB–32 GiB) → Container Apps (0.25–4 vCPU, 0.5–8 Gi)7- **Images**: Registry location (GCR or Artifact Registry), image size, base image8- **Port**: Exposed port (Cloud Run default 8080)9- **Environment Variables**: Static values, secret references, service URLs1011### 2. Request Handling12- **Concurrency**: Per instance (default 80, max 1000) → Container Apps (1–300)13- **Min/Max Instances**: 0–1000 → Container Apps 0–300 per revision14- **Timeout**: Max 60 min → Container Apps max 30 min (1800s)15- **CPU Allocation**: Request-based vs always → Container Apps always allocated16- **HTTP/2, WebSockets, gRPC**: Document if used1718### 3. Networking19- **Ingress**: Public, internal (VPC), or internal + load balancing20- **Custom Domains**: List domains and SSL certificates21- **VPC Connector**: Region, IP range, connected VPC22- **Dependencies**: Cloud SQL, Firestore, Cloud Storage, Pub/Sub, Redis, external APIs2324### 4. IAM & Security25- **Service Account**: Default or custom26- **IAM Roles**: Storage, Firestore, Pub/Sub, Secret Manager, Cloud SQL permissions27- Task role policies → Managed Identity + Azure RBAC28- Secret Manager access → Key Vault RBAC (recommended) or access policies for vaults still using access-policy mode2930### 5. Observability31- **Logging**: Destinations, structured logs (JSON)32- **Monitoring**: Request metrics, CPU/memory, instance count33- **Tracing**: Cloud Trace → Application Insights3435### 6. Event-Driven36- **Eventarc**: Pub/Sub triggers, Cloud Storage triggers37- **Cloud Scheduler**: Schedule (cron), target endpoint3839### 7. Cost Analysis40- Cloud Run: Request charges, CPU/memory time41- Data transfer egress charges42- Container Registry storage4344## Resource Mapping4546| Cloud Run Config | Container Apps Equivalent |47|------------------|--------------------------|48| `--concurrency 80` | `--scale-rule-http-concurrency 80` |49| `--min-instances 0` | `--min-replicas 0` |50| `--max-instances 10` | `--max-replicas 10` |51| `--cpu 1` | `--cpu 1.0` |52| `--memory 512Mi` | `--memory 1Gi` |53| `--port 8080` | `--target-port 8080` |54| `--timeout 300` | ingress timeout 300s |5556## Complexity Rating5758- **Low**: Single container, public ingress, standard env vars, no VPC59- **Medium**: Internal ingress, Pub/Sub triggers, custom service account, Cloud Scheduler60- **High**: Complex traffic management, VPC networking, multiple Eventarc triggers, long-running requests (>30 min)61