【k8s】deploy-maxSurge

環境

1. kubernetes 1.20.4
2. Spring Boot 2.5.0-M3

目標

deploy 在更新過程中，Pod 數量可以超過定義的數量，超過的最大的值就叫 maxSurge。
該值可以是一個百分比，也可以是一個具體的數字，默認情況下，該值為 25%。

示例

Deployment.yaml

apiVersion: apps/v1
kind: Deployment
metadata:
  name: busybox
spec:
  strategy:
    rollingUpdate:
      maxSurge: 0
  selector:
    matchLabels:
      app: busybox
  replicas: 4
  template:
    metadata:
      labels:
        app: busybox
    spec:
      terminationGracePeriodSeconds: 5
      containers:
        - name: busybox
          image: busybox:1.30.0
          command: ["/bin/sh", "-c", "sleep 3600"]

然后將版本升級到 1.31.0。
kubectl set image deployment/busybox busybox=busybox:1.31.0 --record

查看

busybox-76bcb59645-n9w5f   1/1     Terminating         0          48s
busybox-59c95c7d4b-wr6bd   0/1     Pending             0          0s
busybox-59c95c7d4b-wr6bd   0/1     Pending             0          0s
busybox-59c95c7d4b-wr6bd   0/1     ContainerCreating   0          0s
busybox-59c95c7d4b-wr6bd   1/1     Running             0          2s
busybox-76bcb59645-gjg7m   1/1     Terminating         0          50s
busybox-59c95c7d4b-fmzvx   0/1     Pending             0          0s
busybox-59c95c7d4b-fmzvx   0/1     Pending             0          0s
busybox-59c95c7d4b-fmzvx   0/1     ContainerCreating   0          0s
busybox-59c95c7d4b-fmzvx   1/1     Running             0          2s
busybox-76bcb59645-pjfv7   1/1     Terminating         0          52s
busybox-59c95c7d4b-9pv8l   0/1     Pending             0          0s
busybox-59c95c7d4b-9pv8l   0/1     Pending             0          0s
busybox-59c95c7d4b-9pv8l   0/1     ContainerCreating   0          0s
busybox-59c95c7d4b-9pv8l   1/1     Running             0          1s
busybox-76bcb59645-qg4ws   1/1     Terminating         0          53s
busybox-59c95c7d4b-nx6hr   0/1     Pending             0          0s
busybox-59c95c7d4b-nx6hr   0/1     Pending             0          0s
busybox-59c95c7d4b-nx6hr   0/1     ContainerCreating   0          0s
busybox-76bcb59645-n9w5f   0/1     Terminating         0          54s
busybox-76bcb59645-gjg7m   0/1     Terminating         0          56s
busybox-76bcb59645-n9w5f   0/1     Terminating         0          57s
busybox-76bcb59645-n9w5f   0/1     Terminating         0          57s
busybox-76bcb59645-pjfv7   0/1     Terminating         0          58s
busybox-76bcb59645-gjg7m   0/1     Terminating         0          67s
busybox-76bcb59645-gjg7m   0/1     Terminating         0          67s
busybox-76bcb59645-pjfv7   0/1     Terminating         0          67s
busybox-76bcb59645-pjfv7   0/1     Terminating         0          67s
busybox-59c95c7d4b-nx6hr   1/1     Running             0          15s
busybox-76bcb59645-qg4ws   0/1     Terminating         0          68s
busybox-76bcb59645-qg4ws   0/1     Terminating         0          78s
busybox-76bcb59645-qg4ws   0/1     Terminating         0          78s

因為將 maxSurge，最大超出數量設置成了 0，所以無論如何都不會超過定義的數量。
都是先減少再新增，也就是說，更新過程中，只會出現缺少服務數量的情況，不會多。

總結

maxSurge 定義了更新過程中，超出定義的數量，可以是一個數值，也可以是百分比。

附錄