Managed Container Services — Kubernetes Is Often Overkill

~14 min · production

Level 0Container Curious

0 XP0/36 lessons0/10 achievements

0/120 XP to next level120 XP to go0% complete

The spectrum, simply

One container: docker run on a VM (Hetzner, DigitalOcean droplet). Simple. Cheap.
A handful of services: Compose on a single VM, or a managed service: AWS App Runner, Google Cloud Run, Fly.io, Render, Railway.
Many services across many machines: Kubernetes (managed: EKS, GKE, AKS).

When NOT to reach for Kubernetes

Solo dev or small team.
Less than 10 services total.
Compose covers your needs and you can sleep at night.
Learning Docker — finish that first.

What managed services do for you

Cloud Run, App Runner, Container Apps, Fly: you push an image, the platform runs it. They handle SSL, scaling, deploys, restarts. Pay-per-use. Zero Kubernetes ops. For most apps, this is the sweet spot.

Code

Deploy to Cloud Run in one command·bash

# After pushing your image to a registry
gcloud run deploy myapp \
  --image gcr.io/my-project/myapp:1.0 \
  --platform managed \
  --region us-central1 \
  --allow-unauthenticated \
  --memory 512Mi \
  --cpu 1 \
  --max-instances 10

# That's it. Cloud Run gives you HTTPS, scaling, and rollouts.

External links

Exercise

Pick a small project. Estimate three deploy options: (1) Compose on a $5 VM, (2) Cloud Run / Fly.io / Render managed service, (3) Managed Kubernetes (EKS/GKE/AKS). For each: rough monthly cost, ops burden (1-10), and what you'd lose. Pick one and write 2 sentences justifying it.

Progress

Progress is local-only — sign in to sync across devices.

← PreviousRegistries & Tagging — Push Once, Pull Anywhere Next →What's Next — Dev Containers, Wasm, and the Trajectory

Spotted a bug or have feedback on this page?Report an Issue

Comments 0

🔔 Reply notifications (sign in)

No comments yet — be the first.