DEV Community

loading...

explain Kubernetes like I'm five

George Marr
My curiosity is easily stimulated
ใƒป1 min read

explain Kubernetes like I'm five and if you're lucky i may share my legos with you

Discussion (4)

Collapse
bgadrian profile image
Adrian B.G.

When the kindergarten goes to visit a museum or play in the park, you need a couple of grown ups to take care of you.

The grownups are the ones that

  • decide where you go today (on which cluster/server provider)
  • send and filter messages to you (decide what outside messages to deliver to you or not)
  • tell you where to sit (decide on which machine to run)
  • make up pairs of children to play together (locality rules, you may want to group 3 python instances with 1 mysql replica, so they could talk to each other in an optimal way)
  • keep an eye on you (health checks)

One big difference between this example and an orchestrator, is that k8s doesn't hesitate to "kill" instances that misbehave and start new ones.

Collapse
spqrbob profile image
Bob McCann

!remindme 3 days

Wait, this isn't Reddit.

Collapse
danlebrero profile image
Dan Lebrero

Kubernetes is just a Theme Park :)

theme park

Blogged a longer explanation here

Collapse
rhymes profile image
rhymes

My favorite material about this:

Docker runs containers. Kubernetes orchestrates containers. Orchestration is how you stitch multiple containers together into a greater whole: for example, you can have several application containers (and scale out to add more application containers at runtime) talking to a database container. It's possible to do this with Docker alone, but prohibitively complicated at the low level of individual containers. The language of "pods", "services", "deployments", and so on that Kubernetes employs lets you operate at the level of multiple interacting containers instead.