Blog Posts

Kubernetes rollouts are easier to reason about when you model progress separately from success. This post explains why convergence alone is not enough for CI/CD orchestration, how rollout status can be modeled with conditions, and why progress budgets should usually be owned by the platform.

GPU workloads often need hardware-aware placement to avoid silent latency regressions. This post explains what NUMA locality means for Kubernetes GPU nodes, how CPU Manager, Topology Manager, and Memory Manager work together, and the operational gotchas to watch for.

Reflections on using Claude Code for a few weeks—the productivity gains, psychological shifts in how satisfaction moves, and why learning to use coding agents is becoming a non-negotiable skill for software engineers.

In this post, I discuss the scale subresource in Kubernetes and its role in managing resources like Deployments and StatefulSets. I discuss its importance in providing a unified interface for scaling settings in Kubernetes, how it’s used with Horizontal Pod Autoscaler (HPA), Pod Disruption Budget (PDB), and manual scaling with the kubectl scale command. Additionally, the blog covers the significance of the scale subresource for custom resources, explaining how it facilitates integration with rest of the Kubernetes components.

In this post, I share the incident management practices I have picked up over the years as an SRE at Linkedin that help me keep calm under pressure and effectively drive incidents to resolution.

When a pod is scheduled on a kubernetes node, there are various interactions that result into a pod getting an IP address. This post goes into the details of how a pod gets an IP address and describes the interactions between various components - kubelet, CRI Plugin, Container Runtime and CNI Plugins.

Diving into how kubernetes NodePort works and the corresponding iptables rules kube-proxy creates. Also, finding answers to operational questions like what happens when a non-kubernetes process uses a NodePort and whether NodePort continues to work if kube-proxy process dies.