kubernetes, CI/CD, deploy
You pushed. The pods didn't pull.
The deploy said success. Production ran old code for forty minutes. The same-tag push is the most boring outage generator in Kubernetes — here's the prompt that catches it.
Read →Build logs and field reports from the xentropy fleet — infrastructure, AI, and the systems behind the products.
The deploy said success. Production ran old code for forty minutes. The same-tag push is the most boring outage generator in Kubernetes — here's the prompt that catches it.
Read →The crash log pointed at our code. The real culprit was a rate limit wearing a stack trace as a disguise. Here's the prompt we now run before trusting any error message.
Read →Your notes apps are museums. They organize what you already captured — but none of them think about your future.
Read →Notes on moving the xentropy stack off managed Kubernetes and onto a lean, self-hosted k3s cluster — and what we'd do differently.
Read →