3个吊舱，当副本设置为2个时

Question

这是一个Kubectl Description Pod在三个Pod之一上的示例。

Name:         my-helm-release-7679dc8c79-knd9x
Namespace:    my-namespace
Priority:     0
Node:         my-kube-cluster-b178d4-k8s-worker-1/10.1.2.3
Start Time:   Wed, 05 May 2021 21:27:36 -0600
Labels:       app.kubernetes.io/instance=my-helm-release
              app.kubernetes.io/name=my-helm-release
              pod-template-hash=7679dc8c79
Annotations:  
Status:       Running
IP:           10.1.2.4
IPs:
  IP:           10.1.2.4
Controlled By:  ReplicaSet/my-helm-release-7679dc8c79
Containers:
  my-helm-release:
    Container ID:   docker://9a9f213efa63ba8fd5a9e0fad84eb0615996c768c236ae0045d1e7bec012eb02
    Image:          dockerrespository.mydomain.com/repository/runtime/my-helm-release:1.9.0-build.166
    Image ID:       docker-pullable://dockerrespository.mydomain.com/repository/runtime/my-helm-release@sha256:a11179795e7ebe3b9e57a35b0b27ec9577c5c3cd473cc0ecc393a874f03eed92
    Port:           80/TCP
    Host Port:      0/TCP
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       Error
      Exit Code:    139
      Started:      Tue, 11 May 2021 12:24:04 -0600
      Finished:     Tue, 11 May 2021 12:24:15 -0600
    Ready:          False
    Restart Count:  2509
    Liveness:       http-get http://:http/ delay=0s timeout=1s period=10s #success=1 #failure=3
    Readiness:      http-get http://:http/ delay=0s timeout=1s period=10s #success=1 #failure=3
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-82gnm (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  default-token-82gnm:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-82gnm
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  
Tolerations:     node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                 node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason     Age                      From     Message
  ----     ------     ----                     ----     -------
  Warning  Unhealthy  10m (x3758 over 5d15h)   kubelet  Readiness probe failed: Get http://10.1.2.4:80/: dial tcp 10.1.2.4:80: connect: connection refused
  Warning  BackOff    15s (x35328 over 5d14h)  kubelet  Back-off restarting failed container

Answer 1

需要什么（从掌舵人的角度来看）让副本数量降到我设定的极限？

你的豆荚需要处于“健康”状态。那么它们就在你想要的副本数量中。

首先，您部署了3个副本。这是由副本集管理的。