Kubernetes Rolling Updates and Rollback: A Practical Guide
Upgrade a Kubernetes Deployment safely with RollingUpdate, monitor progress, verify revisions, and roll back instantly if needed.
Loading…
ReadMeFeed / Community knowledge
#rolling-update
Real questions. Useful conversations. Find the people who know your stack.
kubernetesChoosing Between RollingUpdate and Recreate Deployments in OpenShift
Decide when to use RollingUpdate versus Recreate for OpenShift Deployments, then patch and validate the strategy.
redhatAnsible Execution Strategies: Linear, Free, and Serial
Choose between Ansible linear, free, and serial execution strategies based on synchronization, runtime, and blast radius. Includes validation steps.
ansibleZero-Downtime Rolling Updates for Stateless Kubernetes Deployments
Update a Kubernetes Deployment image with readiness probes, rolling-update limits, and rollback for zero-downtime releases.
Scalingo Zero‑Downtime Deployments: How Rolling Updates Keep Your App Online
Discover how Scalingo’s rolling‑update deployment keeps services online, how to verify it, and the trade‑offs you should watch for.
scalingoZero‑Downtime Rolling Updates for Nomad Jobs: A Step‑by‑Step Guide
A concise, step‑by‑step guide to performing zero‑downtime rolling updates of a Nomad job, covering prerequisites, job configuration, deployment commands, validation checks, and rollback options.
nomadPerform a Safe Rolling Update of a Kubernetes Deployment
Learn how to update a Deployment’s container image with zero downtime by using kubectl, verifying the rollout, and reverting if needed.
Nomad rolling update leaves TCP connections unresolved during migration
Goal: Determine whether Nomad's default rolling update behavior, which waits for a new allocation to pass its health check before stopping the old one, ensures zero‑downtime for small applications that rely on long‑lived TCP connections. Constraints: The update stanza can be tuned with max_parallel and health check intervals, but Nomad does not offer a built
Docker Swarm rolling update on Raspberry Pi leaves in‑memory cache stale after task replacement
Goal: achieve a zero‑downtime migration of a small application on a Raspberry Pi Docker Swarm cluster while preserving any in‑memory state such as caches or session data during a rolling update. Constraint: Docker Swarm’s rolling update mechanism drains the old task, waits for the replacement to become healthy, and then proceeds, but it provides no built‑in
raspberrypi