Konrad Kowalski (rootsher)Principal Platform & Reliability Architect100001111001011011100011010110011000100100100010

Containers

posts (23)

  1. The OSI Model in the Cluster and the Cloud: Who Sees What When You Open a Page

    L3, L4 and L7 are shorthand for how deeply a piece of infrastructure looks into traffic. One request, from clicking "Pay" to the payments pod, layer by layer.

  2. CPU in Kubernetes from the kernel up12/12

    Anatomy of a CPU problem: from an understated request to p99 latency

    One incident end to end: a 500m request, no limit, no throttling, and p99 climbing from 35 to 180 ms. The whole path of the mechanism.

  3. CPU in Kubernetes from the kernel up11/12

    Noisy neighbor and CPU overcommit: when one Pod breaks another

    Overcommit works until bursts become correlated. An understated request is not only about placement - it is a weaker position under contention.

  4. Kubernetes from the Inside: Cluster Architecture Basics7/7

    Managed, Self-managed, Cloud, On-premises, VM and Bare Metal

    Managed, cloud and bare metal are not three alternatives but three separate questions - who manages Kubernetes, where the infrastructure runs and what the…

  5. CPU in Kubernetes from the kernel up8/12

    Why 1 CPU does not mean one core

    CPU time and CPU placement are two different mechanisms. A limit says how much you may consume; affinity and cpuset say where a task may execute.

  6. Kubernetes from the Inside: Cluster Architecture Basics6/7

    How Kubernetes Components Work Together

    One workload from kubectl apply to a running Pod, step by step through the API Server, etcd, controllers, the scheduler, the kubelet, the runtime and CNI…

  7. Kubernetes from the Inside: Cluster Architecture Basics5/7

    DNS and CoreDNS in Kubernetes

    A Pod's IP address is a poor interface for applications, because it changes. CoreDNS turns a stable name into a Service IP, and only then the datapath delivers…

  8. CPU in Kubernetes from the kernel up7/12

    Requests, Limits and QoS: how Kubernetes classifies Pods

    A QoS class is the result of how requests and limits are configured, not a separate CPU allocation mechanism. Guaranteed is not a dedicated core.

  9. 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…

  10. 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…