World map

 

BM

World K1: The Food Court

When not to use Kubernetes

You will learn: when a simpler home for your app is the smarter choice.

Checked with Kubernetes 1.37 on 31 Oct 2026

The problem

Aina sells kuih online. Her site gets 30 visits a day. Her cousin says: “Put it on Kubernetes!” Good idea?

Watch

Tap each point on the timeline.

A food court needs staff even with no customers. That is overhead: The work and machines a tool needs just to keep running, before your app does anything.: work and machines just to keep it open. Tap through a year with your own cluster.

Try it

Kubernetes, or something simpler? Sort each app.

Drag a card into a box. Or tap the card, then tap the box.

      Check

      Put these homes in order, from least work to most work.

      Least work at the top. Put these in order. Use the arrows, or drag.

      • A Kubernetes cluster
      • A few containers with Compose
      • One container on one server
      • A static host (just files)

      Check

      Good reason to pick Kubernetes, or needs work? Swipe each one.

      Swipe right for good, left for needs work. Or use the buttons.

      1 / 4

      Our 30 services must stay up through a machine failure

      You did it!

      You can now tell when Kubernetes is worth it, and when it isn’t.

      Go deeper (optional)

      Managed Kubernetes, like EKS, GKE or AKS, runs the manager’s office for you. You still look after your apps and pay for the machines.

      Fun fact: this course is a static site. It runs without Kubernetes.

      Real rep (optional): look up how your favourite app is hosted. Is it big enough to need a cluster?