-
-
Notifications
You must be signed in to change notification settings - Fork 27
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
FAQ:Zero downtime app updates (#396)
* add FAQ:Zero downtime app updates * Update how-achieve-zero-downtime-apps.md Co-authored-by: Erik Osterman <[email protected]>
- Loading branch information
Showing
1 changed file
with
20 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
--- | ||
title: "How do we achieve app updates with zero downtime?" | ||
description: "Kubernetes out-of-the-box supports zero-downtime updates." | ||
tags: | ||
- zero downtime | ||
- Kubernetes | ||
- apps | ||
- updates | ||
--- | ||
|
||
## Question | ||
|
||
How do we achieve zero-downtime deploys of app updates? | ||
|
||
|
||
## Answer | ||
|
||
Kubernetes out-of-the-box supports zero-downtime rolling updates. The key is to set the `StrategyType` of the deployment to `RollingUpdate` (which is the default). Additionally, setting `maxUnavailable` to a small number ensures that updates will stop if pods stop dropping offline due to failed health or readiness probes. | ||
|
||
Note: This requires applications to implement proper readiness and liveness probes so Kubernetes is able to assess availability. Additionally, the more an application has support for the notion of health, the more reliable it will be. We recommend splitting liveness from readiness probes, so they respond appropriately. |