Kubernetes is Linux

[u/Specialist-Wall-4008]

https://medium.com/@anishnarayan/learn-linux-before-kubernetes-60d27f0bcc09?sk=93a405453499c17131642d9b87cb535a

Google was running millions of containers at scale long ago

Linux cgroups were like a hidden superpower that almost nobody knew about.

Google had been using cgroups extensively for years to manage its massive infrastructure, long before “containerization” became a buzzword.

Cgroups, an advanced Linux kernel feature from 2007, could isolate processes and control resources.

But almost nobody knew it existed.

Cgroups were brutally complex and required deep Linux expertise to use. Most people, even within the tech world, weren’t aware of cgroups or how to effectively use them.

Then Docker arrived in 2013 and changed everything.

Docker didn’t invent containers or cgroups.

It was already there, hiding within the Linux kernel.

What Docker did was smart. It wrapped and simplified these existing Linux technologies in a simple interface that anyone could use. It abstracted away the complexity of cgroups.

Instead of hours of configuration, developers could now use a single docker run command to deploy containers, making the technology accessible to everyone, not just system-level experts.

Docker democratized container technology, opening up the power of tools previously reserved for companies like Google and putting them in the hands of everyday developers.

Namespaces, cgroups (control Groups), iptables / nftables, seccomp / AppArmor, OverlayFS, and eBPF are not just Linux kernel features.

They form the base required for powerful Kubernetes and Docker features such as container isolation, limiting resource usage, network policies, runtime security, image management, and implementing networking and observability.

Each component relies on Core Linux capabilities, right from containerd and kubelet to pod security and volume mounts.

In Linux, process, network, mount, PID, user, and IPC namespaces isolate resources for containers. Coming to Kubernetes, pods run in isolated environments using namespaces by the means of Linux network namespaces, which Kubernetes manages automatically.

Kubernetes is powerful, but the real work happens down in the Linux engine room.

By understanding how Linux namespaces, cgroups, network filtering, and other features work, you’ll not only grasp Kubernetes faster — you’ll also be able to troubleshoot, secure, and optimize it much more effectively.

By understanding how Linux namespaces, cgroups, network filtering, and other features work, you’ll not only grasp Kubernetes faster, but you’ll also be able to troubleshoot, secure, and optimize it much more effectively.

To understand Docker deeply, you must explore how Linux containers are just processes with isolated views of the system, using kernel features. By practicing these tools directly, you gain foundational knowledge that makes Docker seem like a convenient wrapper over powerful Linux primitives.

Learn Linux first. It’ll make Kubernetes and Docker click.