Containers
posts (23)
- 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.
Cluster Policies: Why Kyverno and CEL Exist
Cluster policies appeared because RBAC says who may create a resource, but it does not answer well whether this specific YAML is safe.
Introduction to Service Mesh: Why Istio and Linkerd Exist
Service mesh appeared because, in a microservice system, traffic, identity, and observability problems started repeating in every service.
- Gateway API Without the Magic4/4
Migrating from ingress-nginx to Gateway API
Migrating from ingress-nginx is not mechanical YAML translation. First, separate the application contract from controller-specific behavior.
- Gateway API Without the Magic3/4
GatewayClass: A Contract With the Implementation
GatewayClass is not an environment label. It is where Kubernetes Gateway API meets a specific controller.