Public Explanation as a Test of an Engineering Solution
How a public draft helps reconstruct a causal chain, expose hidden dependencies, and define the guarantees of an engineering solution.
gitops
How CI/CD and Flux Split Responsibilities in My DocOps Project
How an article moves through two repositories, where CI ends, and which part of delivery belongs to Flux.
Why CI in a GitOps Repository Is Not a Deployment Gate
Why CI could not block Flux after a direct push and how a Merge Request with auto-merge moved validation before the watched branch.
How to Preserve Engineering Knowledge from Tickets and Chats
How to turn ticket histories and chat discussions into documentation, checks, and automation that engineers can reuse.
A Ready Node Can Still Drift from Its Baseline
A green Ready status and a correct node configuration are not the same guarantee. I ran into that distinction while standardizing kubelet settings across several node classes in a Kubernetes cluster I operated. Each class had a configuration baseline stored in Git. It defined resource reservations, eviction thresholds, and image garbage collection settings. Kubernetes reported the nodes as Ready, yet a separate check found that the local /var/lib/kubelet/config.yaml on some of them no longer matched the expected file. ...