Gap-9: Container Apps Migrate (F → A) — ECS/Fargate + Cloud Run migration guides

[paulyuk]

Parent: #1608

Container Apps Migrate: F → A

Learning from: Functions Migrate (A) — same 4-phase pattern, adapted for containers

Current state: Zero coverage. GCP mentioned in triggers only, no scenario guidance.

Deliverables

• references/services/container-apps/ecs-to-container-apps.md — Full migration guide:
  • Task definitions → Container App YAML specs
  • Service definitions → Container App revisions + ingress
  • Fargate launch type → Consumption plan
  • ECR → ACR migration (image transfer)
  • ECS Service Connect → Container Apps service discovery
  • App Mesh → Dapr integration
• references/services/container-apps/cloud-run-to-container-apps.md — GCP migration guide:
  • Cloud Run service/revision → Container App/revision (very similar model)
  • Artifact Registry → ACR
  • Cloud Run Jobs → Container Apps Jobs
  • Secret Manager → Key Vault
• Container-specific assessment template (image analysis, port mapping, env vars, secrets, volumes)
• Add routing rules in azure-cloud-migrate for ECS/Fargate/Cloud Run keywords
• Add trigger tests for Container Apps migration prompts
• Add 1 integration test with a real ECS or Cloud Run sample app

Key Service Mappings

AWS ECS / GCP Cloud Run	Azure Container Apps
Task Definition / Cloud Run YAML	Container App spec
Fargate / Cloud Run serverless	Consumption plan
ECR / Artifact Registry	Azure Container Registry
ECS Service Connect / Cloud Run svc	Container Apps service discovery
ALB / Cloud Run ingress	Container Apps ingress
App Mesh / Istio	Dapr
CloudWatch / Cloud Logging	App Insights + Log Analytics

Priority: P0 — Migration is the worst equity gap.

⚠️ Starting assessment — domain experts should modify or contribute what they believe is essential.

[github-actions]

Thanks for opening this, Paul Yuknewicz (@paulyuk)! 🙌

This issue has been labeled enhancement since it requests new migration guide content, and azure-cloud-migrate as it directly extends that skill with ECS/Fargate and Cloud Run coverage. The skills label was also added since the work touches skill routing rules, trigger tests, and integration tests. Since this involves concrete coding work (new reference docs, routing rules, trigger tests, and an integration test), assign-to-copilot has been applied — a coding agent will take a look and can help with the implementation.

Generated by Issue Triage for issue #1617 · ◷

[paulyuk]

Resolved by the Container Apps team's merged migration guides (#1534 Fargate/ECS, #1567 Cloud Run), which also add Kubernetes and Spring coverage. These supersede the draft PR #1634 (now closed). Gap-9 (Container Apps Migrate → A) is achieved.