What transfers
Your Docker experience already covers this
Container
→ Pod
Docker runs individual containers; Kubernetes schedules pods, usually one app container plus optional sidecars, as the smallest deployable unit.
docker run
→ Deployment manifest
A one-off container command becomes a declarative desired state that Kubernetes continuously reconciles.
Port mapping
→ Service and ingress
Local port exposure turns into stable service discovery and optional external routing through ingress controllers.
What's new
Where Kubernetes asks you to think differently
Kubernetes is built around pods, deployments, services, ingress, config maps, secrets, and controllers. Expect to spend real time on:
pods
deployments
services
ingress
Sample topics
3 of the 17 curated topics on this roadmap
Container Basics
A Food Delivery Platform's backend team is modernizing deployment — moving from manually configured servers where 'it works on my machine' problems delay releases, to a consistent, portable unit that runs identically in development, CI,…
Images
A Learning Platform's team needs to package their Node.js API into a container image — choosing a minimal base image, layering dependencies efficiently for fast builds and small image sizes, and pushing to a registry for Kubernetes to pull…
Containers
A CRM backend team needs to run their application container with CPU and memory limits to prevent one misbehaving container from starving others, with health checking to automatically restart crashed containers, and with…
14 more topics, in order, with side-by-side Docker and Kubernetes code, are in your roadmap after signup.
Create a free account to see your full roadmapOther switches
Related stack switches
Want the longer concept-by-concept comparison? Read the Docker to Kubernetes overview.