From 6f9635c42a0f24721bb31f54f38187b813816003 Mon Sep 17 00:00:00 2001 From: Takuya N Date: Tue, 26 Jun 2018 18:26:51 +0900 Subject: [PATCH] Fix markdown for blog: 2018-04-30-zero-downtime-deployment-kubernetes-jenkins (#8920) --- .../2018-04-30-zero-downtime-deployment-kubernetes-jenkins.md | 1 + 1 file changed, 1 insertion(+) diff --git a/content/en/blog/_posts/2018-04-30-zero-downtime-deployment-kubernetes-jenkins.md b/content/en/blog/_posts/2018-04-30-zero-downtime-deployment-kubernetes-jenkins.md index e61b74cd2d..e7a70c7cad 100644 --- a/content/en/blog/_posts/2018-04-30-zero-downtime-deployment-kubernetes-jenkins.md +++ b/content/en/blog/_posts/2018-04-30-zero-downtime-deployment-kubernetes-jenkins.md @@ -10,6 +10,7 @@ Ever since we added the [Kubernetes Continuous Deploy](https://aka.ms/azjenkinsk ## Rolling Update Kubernetes supports the RollingUpdate strategy to replace old pods with new ones gradually, while continuing to serve clients without incurring downtime. To perform a RollingUpdate deployment: + * Set `.spec.strategy.type` to `RollingUpdate` (the default value). * Set `.spec.strategy.rollingUpdate.maxUnavailable` and `.spec.strategy.rollingUpdate.maxSurge` to some reasonable value. * `maxUnavailable`: the maximum number of pods that can be unavailable during the update process. This can be an absolute number or percentage of the replicas count; the default is 25%.