whoami
Deep technical notes on operating systems, virtualization, and cloud-native infrastructure — kernels, filesystems, emulation, and the history behind the tools that keep systems running.
A helm upgrade fails partway, or a release gets stuck in 'pending-upgrade' state, blocking every subsequent operation on it. Here's how to actually recover instead of getting stuck retrying the same failing command.
A pod can't start because Kubernetes can't pull its container image — the fix depends entirely on which of a handful of specific causes is actually responsible, from a typo to a private registry auth problem.
kubectl get nodes shows a node stuck in NotReady state, and pods are being evicted from it. Here's how to check kubelet, container runtime, and network plugin health in the right order.
A container gets killed repeatedly with reason OOMKilled, even though the application 'shouldn't' need that much memory. Here's how to find its actual peak usage and set limits that reflect reality instead of guesses.
A pod stuck Pending means the scheduler couldn't place it anywhere — here's how to read the actual reason from pod events instead of guessing at resource, taint, or affinity problems.
terraform init fails with incompatible provider version constraints, or plan produces unexpected changes after an update. Here's how to read the constraint error and pin versions correctly across a team.
A complete walkthrough using Flagger to automate a canary rollout that promotes or rolls back based on real metrics — no human needing to watch a dashboard and decide manually.
A complete walkthrough setting up ArgoCD so a Git repository becomes the single source of truth for your cluster state — deploy by merging, not by running kubectl commands manually.
A complete walkthrough restricting which pods can talk to which — Kubernetes allows all pod-to-pod traffic by default, and NetworkPolicies are how you actually change that.
A complete walkthrough setting PodDisruptionBudgets so voluntary disruptions — node drains, cluster upgrades — never take down more replicas of a service than it can actually tolerate at once.