What is Kubernetes?
Summary: Kubernetes is four things at once — an orchestration engine, a declarative API, an ecosystem of tools, and a flagship project of the CNCF. This lesson gives a rigorous definition, explains the origin of the name (the Greek pilot), retraces the fascinating history from Borg at Google in 2003, and demonstrates why Kubernetes became the world standard in 2026.
1. Rigorous definition on four levels
The word "Kubernetes" covers four realities that must be distinguished.
In everyday usage, "Kubernetes" mostly refers to meanings 1 and 2 — the engine and the API. When an engineer says "we are going to migrate to Kubernetes", they mean "we are going to manage our deployments via the Kubernetes API and let the engine orchestrate".
A one-sentence definition for an interview:
Kubernetes is an open source container orchestration system, started by Google in 2014 and maintained since 2015 by the Cloud Native Computing Foundation. It automates the deployment, scaling, resilience and network management of containerized applications across dozens to thousands of machines, from a declarative YAML API.
Memorize this sentence. It answers 90% of recruiters' questions about Kubernetes.
2. The name Kubernetes — from the Greek for "pilot"
Unlike Docker (the maritime container analogy) or Terraform (the terraforming analogy), the name Kubernetes comes from ancient Greek.
Official pronunciation: "koo-ber-net-eez". To avoid in an interview: mangled pronunciations that betray unfamiliarity with the project.
Three ways to say "Kubernetes" in a tech conversation:
- Kubernetes — the full name, more formal
- K8s — written, very frequent in slides and documentation
- Kube — informal, used among insiders ("let's kube-apply that")
3. How Kubernetes works — the principle in one image
To understand Kubernetes, you only need to remember this mental image.
This 6-step cycle, with a permanent convergence loop, is the heart of Kubernetes. You repeat this workflow dozens of times a day in a team that uses K8s intensively.
No container is launched manually. You describe, Kubernetes executes and maintains. This is called the convergent declarative model.
4. A short chronology — Kubernetes' trajectory over 23 years
Kubernetes did not come out of nowhere. Its history begins well before 2014.
A remarkable fact: Kubernetes went from a Go project published by 3 Google engineers in 2014 to the invisible infrastructure of half the world's internet in 2026. One of the fastest trajectories in software history.
5. The CNCF — the lungs of Kubernetes
Kubernetes would never have won if it had remained Google proprietary. The CNCF (Cloud Native Computing Foundation) is the secret of its success.
A key strategic virtue: because no company controls Kubernetes, all the major companies rallied to it — even Google's competitors. Amazon resisted for a long time, before giving in in 2017 with EKS. Today it is impossible to be credible in the cloud without supporting Kubernetes.
6. Kubernetes in 2026 — the key figures
Compare with 2014: an unknown project, 3 developers, a few dozen early adopters. In 12 years, Kubernetes has become the invisible backbone of half the world's internet.
7. Vanilla Kubernetes, distributions, managed — what to choose
There are three main ways to use Kubernetes in 2026.
Simple rule for 2026:
- To learn → minikube or kind locally.
- For a project in production → EKS, GKE or AKS — a managed cloud.
- For a large company with support → OpenShift or Rancher.
- For edge and IoT → k3s (lightweight, popular).
Lesson 6 goes deeper into each of these options.
8. Kubernetes certifications — the calling card
Three official CNCF certifications validate Kubernetes skills.
A notable fact: these certifications are 100% practical (no MCQ). They evaluate your real ability to work with Kubernetes under pressure, in a real terminal, with the real online documentation available during the exam.
The Premium Kubernetes Course includes targeted preparation for the CKAD — the most accessible certification to start with.
Remember in 30 seconds
- Kubernetes = orchestration engine + declarative API + ecosystem + CNCF project.
- Origin: Google's Borg project since 2003, open source in 2014, CNCF in 2015.
- Name: from the Greek κυβερνήτης, "ship's pilot". Abbreviated K8s (8 letters between K and s).
- Pronunciation: "koo-ber-net-eez".
- 2026 adoption: 90%+ of large tech companies.
- Three usage modes: vanilla, enterprise distribution, managed cloud.
- Three CNCF certifications: CKAD (dev), CKA (admin), CKS (security).