13.2.2.5 Managed Container Target

A managed container target deploys an application's image to a cloud provider's own managed container service — AWS Fargate, Google Cloud Run, Azure Container Apps — handling the underlying infrastructure (servers, scaling, networking) automatically, without requiring the team to operate their own cluster at all.

Deploying to a Managed Container Service

Deployment typically involves a single command or API call referencing the image, with the provider handling everything else.

gcloud run deploy myapp --image=registry.example.com/myapp:1.0 --platform=managed --region=us-central1

This single command deploys the image to Cloud Run, with Google handling scaling, networking, and underlying infrastructure entirely.

Why This Removes Cluster Operations Burden Entirely

Unlike Kubernetes or Swarm, where the team itself must operate and maintain the underlying cluster, a managed container service shifts that operational responsibility entirely to the cloud provider.

aws ecs update-service --cluster mycluster --service myapp --force-new-deployment

Even AWS Fargate, technically using ECS underneath, removes the need to manage the underlying EC2 instances a traditional ECS deployment would otherwise require.

Why This Approach Trades Some Control for Simplicity

A managed service typically offers less fine-grained control over the underlying infrastructure than self-managed Kubernetes or Swarm, a reasonable trade for teams prioritizing operational simplicity over that additional control.

gcloud run services describe myapp --region=us-central1

When a Managed Container Target Is a Particularly Good Fit

Teams without the capacity or need to operate their own cluster infrastructure, or applications with traffic patterns well-suited to a managed service's automatic, often request-based scaling model, are particularly good fits for this delivery target.

gcloud run deploy myapp --image=registry.example.com/myapp:1.0 --min-instances=0 --max-instances=20

Why a Managed Container Target Matters

For teams wanting container deployment without the operational overhead of running their own cluster, a managed container service provides a meaningfully simpler delivery target, trading some infrastructure control for considerably reduced operational burden.