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 a 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 does not block Flux after a direct push, and how a Merge Request with required checks moves 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. Consider several node classes with configuration baselines in Git. The baselines define resource reservations, eviction thresholds, and image garbage collection settings. Actual host files can differ from those baselines while Kubernetes continues reporting the nodes as ready. This scenario lets us examine the problem without describing a particular cluster or operations tool. A node can work now yet react differently from its peers once memory or disk becomes scarce. ...