yceffort
06 POSTS

Kubernetes 1

  • ◆ Kubernetes for Frontend Developers Part 5
    #kubernetes#devops#web-performance

    Autoscaling Is Automatic but Not Instant: HPA's Timeline, Measured Segment by Segment

    Raise traffic 12x and it takes 31.5 seconds for a new pod to receive its first request, 22.5 of them spent before the HPA notices the load. The post also covers the conditions under which the autoscaler stops responding in the five minutes right after a deploy, why scale-down comes down in steps, why memory-based HPA does not fit Node apps, and scaling ahead of time with KEDA.

    25 min read
  • ◆ Kubernetes for Frontend Developers Part 4
    #kubernetes#devops#debugging

    How Do Pods Terminate? Measuring the Causes and Fixes of Deploy-Time Errors

    Even a deploy that changes not a single line of code still fails requests. I tagged every failed request during rolling deploys by type and timestamp, found four causes, and added fixes one at a time until failures reached zero. The post also checks the actual Next.js shutdown code and the real CrashLoopBackOff restart intervals.

    Updated 20 min read
  • ◆ Kubernetes for Frontend Developers Part 3
    #kubernetes#networking#devops

    How Does Traffic Reach My Pod? From ClusterIP to port-forward

    A Service's ClusterIP is an IP attached to no machine, so how does a curl request reach a pod? In a kind cluster, this post inspects iptables rules and conntrack, EndpointSlice, cluster DNS and ndots, Gateway, and port-forward in turn to follow the path a request takes.

    27 min read
  • ◆ Kubernetes for Frontend Developers Part 2
    #kubernetes#docker#devops

    How My Next.js App Becomes a Pod: A Record of Opening Up Containers and Pods

    The same Next.js app produced one 1.72GB image and one 208MB image. This post traces the missing 1.5GB back through the layers, and verifies with PIDs and cgroup files that a container is an isolated process.

    Updated 19 min read
  • ◆ Kubernetes for Frontend Developers Part 1
    #kubernetes#devops

    A Kubernetes Concept Map for Frontend Developers: From Pods to Autoscalers

    The Kubernetes vocabulary and structure that frontend developers running SSR actually encounter, organized in the order of real work: cluster structure, deploys, pod state and resources, the traffic path, and autoscaling.

    Updated 22 min read
  • ◆ Kubernetes for Frontend Developers Part 6
    #memory#nodejs#kubernetes

    Why Is Your Node.js Pod That Size? Sizing Measured Firsthand, from NODE_OPTIONS to Pod Count

    I added one GC tuning flag to the same workload and peak RSS rose from 201MB to 593MB while the live data stayed the same. This post measures V8 New Space directly to trace why, and proposes three criteria frontend developers can use to size a Node.js pod.

    Updated 45 min read