14 Automating releases with upgrades and rollbacks
Updating containerized applications should be a zero-downtime process that is managed by the container orchestrator. You typically have spare compute power in your cluster that managers can use to schedule new containers during updates, and your container images have health checks so the cluster knows if the new components fail. Those are the enablers for zero-downtime updates, and you’ve already worked through the process with Docker Swarm stack deployments in chapter 13. The update process is highly configurable, and we’ll spend time exploring the configuration options in this chapter.
Tuning update configuration might sound like a topic you can safely skip, but I can tell you from my own ...
Get Learn Docker in a Month of Lunches now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
