Kubernetes: when it is worth it
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
decide whether an organization should run Kubernetes at all.
Planned topics
- Kubernetes gives portability, a large ecosystem, fine-grained control, and complex workload scheduling.
- It also brings upgrades, networking, security policy, observability, and a steep learning curve, even when managed.
- Worth it when: many services, multiple teams, platform team exists, workloads need its features.
- Not worth it when: a handful of services, a small team, simple needs.
- A managed container service or PaaS is the default; Kubernetes needs a justification.
Draft outline details
Demonstration
a checklist with yes/no: more than 15 services, dedicated platform team, need for custom operators or multi-cloud portability, existing skills. Three or more "yes" answers supports Kubernetes.
Check your understanding
A six-person team with four services considers Kubernetes. Default advice?
Show answer
Use a managed container platform; revisit if scale and team grow.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.