Tag
CI/CD
← Clear filter
OperationsZero-downtime deployments on Kubernetes: readiness, rolling updates and rollback
The rollout was green, yet users saw 502 errors for 20 seconds. What a rolling update alone does not give you: readiness, a clean shutdown, disruption budgets, migrations in two steps and a rollback to a pinned version.
- Kubernetes
- CI/CD
ArchitectureGitOps with Argo CD or a control plane? What teams without a platform team actually need
GitOps with Argo CD brings review, history and drift correction – plus a second repository, a secrets strategy and a tool that needs looking after. What small teams actually need, and when GitOps is still the better choice.
- Kubernetes
- CI/CD
ArchitectureA Heroku alternative in Europe: from PaaS to your own cloud without a platform team
Since February 2026 Heroku has stopped building new features. What you have to replace when you move – from the build to the Postgres add-on –, which options exist in Europe and how the migration works, step by step.
- Migration
- Scaleway
- CI/CD
OperationsKubernetes in production: the checklist most architecture diagrams leave out
Popular Kubernetes production architecture diagrams usually stop at the registry. This checklist starts there: rollback, secrets, TLS, resources, backups with tested restores, security, alerts, upgrades and the question of who owns the cluster.
- Kubernetes
- Backups
- CI/CD
OperationsRollbacks on Kubernetes: why a tag is not a version
A rollback that pulls the same tag again brings back the broken version. If you want to roll back reliably, you need the digest of every deployment, and a plan for the database.
- CI/CD
- Kubernetes
- Backups
OperationsIn the cluster or on GitHub Actions: where should the image be built?
A build in the cluster runs where the application runs. GitHub Actions builds where the code lives. Neither needs a Docker daemon, and both have a catch you only notice in production.
- CI/CD
- Kubernetes
- Costs