Frigga Blogs

Kubernetes' built-in Deployment has exactly one automated deployment strategy, the rolling update, and it is far less careful than most teams assume. It replaces old pods with new ones a few at a time, but the moment a new pod passes its…

No serious team merges application code without a review, a record of who changed what, and a way to undo it. Then those same teams build their entire cloud, the servers, databases, networks, and permissions that the code runs on, by clickin…

Ask a team how they roll back and many will say they re-run the pipeline on the previous commit. That is not a rollback. Even with identical source code, a rebuild can produce a different artefact, because dependencies, base images, and buil…

The promise of a staging environment is simple and appealing: it is a near-copy of production, so if your change works there, you can be confident it will work in production ( All Quiet, 2026 ). That confidence is the problem, because stagin…

Most teams can recite the four DORA metrics and could not tell you their own. The usual reasons are that measuring them sounds like a project, or that it means buying a platform. Neither is true if you deploy through GitHub, because the data…

Ask most teams to show you exactly how their production environment is configured, and the honest answer is that they cannot, because the only complete record of it is the running system itself. The real state lives in the cluster and in the…