ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Upgrade a Kubernetes Deployment safely with RollingUpdate, monitor progress, verify revisions, and roll back instantly if needed.
Decide when to use RollingUpdate versus Recreate for OpenShift Deployments, then patch and validate the strategy.
Choose between Ansible linear, free, and serial execution strategies based on synchronization, runtime, and blast radius. Includes validation steps.
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.
Migration Strategy Trade-offs A small stateless application requires a migration strategy that ensures zero downtime. Two documented Kubernetes patterns are under consideration: a RollingUpdate with maxSurge=0 and maxUnavailable=1 , or a Blue-Green deployment using separate Services and selector updates. Constraints and Uncertainties The maxSurge=0 approach
kubernetes
redhat
ansible
nomad