Kubernetes
posts (32)
- Kubernetes from the Inside: Cluster Architecture Basics4/7
Networking in Kubernetes
CNI gives Pods their addresses and connectivity, while kube-proxy or an eBPF datapath makes traffic sent to a Service's virtual address reach the right…
- Kubernetes from the Inside: Cluster Architecture Basics3/7
The Worker Node and the Data Plane
The control plane decides, but the worker node executes - the kubelet looks after the Pods assigned to the machine and, through CRI, asks the container runtime…
- CPU in Kubernetes from the kernel up6/12
PSI: how Linux measures real CPU pressure
Utilisation says how much CPU a workload got. PSI measures the time it lost because it wanted to execute and had nothing to execute on.
- Kubernetes from the Inside: Cluster Architecture Basics2/7
The Kubernetes Control Plane
The control plane is not one brain but four components with separate roles - the API Server communicates, etcd stores the state, the scheduler picks a node and…
- Kubernetes from the Inside: Cluster Architecture Basics1/7
Kubernetes Cluster Architecture
Before taking Kubernetes apart into processes, a simple map of the whole - the control plane decides and guards the state, the data plane does the work, and in…
- series · 7 parts
Kubernetes from the Inside: Cluster Architecture Basics
A series about what actually makes a Kubernetes cluster work - from kube-apiserver and etcd, through kubelet and CNI, to the managed vs self-managed choice and…
- CPU in Kubernetes from the kernel up4/12
CPU Limits and throttling: what a CPU limit really does
A limit does not pin a container to a core. It gives it a CPU-time budget accounted per period, and once that runs out the kernel throttles it.
- CPU in Kubernetes from the kernel up3/12
CPU Requests in Kubernetes: what they really are
A request is a declaration of demand, not a ceiling. It feeds placement in kube-scheduler and CPU weight on the kernel side.
- series · 12 parts
CPU in Kubernetes from the kernel up
A CPU model built bottom-up: from runnable tasks and the scheduler, through cgroups, requests and limits, to throttling, contention, PSI and diagnostics.
- Deployment Strategies: Why They Exist6/6
Shadow Traffic: Testing Without Responding to the User
Shadow traffic sends a copy of a request to the new version, but the user receives the old version's response. It tests behavior without taking over traffic.