horizo ntalpodautoscaler min和max replica是1创建2个pod

Question

我正在尝试运行horizo​​ntalpodautoscaler资源定义混合和最大副本为1.不知何故，一旦它开始运行pod的两个实例同时运行，然后1个pod终止。结束状态我有1个pod运行。

这是HPA资源的正常行为，它以某种方式创建了具有2个pod的复制集，即使最大值为1

谢谢

Answer 1

一般情况下不会发生。如果hpa目标度量标准目标非常低并且启动应用程序超过目标CPU阈值导致pod的扩展，则可能发生这种情况。

您可以检查HPA状态，events section可以解释缩放的原因。

HPA状态：kubectl描述HPA_NAME

请查看以下示例以供参考

    Metrics:                                               ( current / target )
  resource cpu on pods  (as a percentage of request):  40% (406m) / 50%
Min replicas:                                          10
Max replicas:                                          100
Conditions:
  Type            Status  Reason              Message
  ----            ------  ------              -------
  AbleToScale     True    ReadyForNewScale    the last scale time was sufficiently old as to warrant a new scale
  ScalingActive   True    ValidMetricFound    the HPA was able to succesfully calculate a replica count from cpu resource utilization (percentage of request)
  ScalingLimited  False   DesiredWithinRange  the desired replica count is within the acceptible range
Events:
  Type    Reason             Age                   From                       Message
  ----    ------             ----                  ----                       -------
  Normal  SuccessfulRescale  35m (x1216 over 12d)  horizontal-pod-autoscaler  New size: 10; reason: All metrics below target

Answer 2

这些是来自所有相关资源的事件：

HPA Events:
NAME            REFERENCE                  TARGETS         MINPODS   MAXPODS   REPLICAS   AGE
example-ms   Deployment/example-ms   <unknown>/50%   1         1         0          0s
example-ms   Deployment/example-ms   <unknown>/50%   1         1         0         1s
example-ms   Deployment/example-ms   <unknown>/50%   1         1         2         3s
example-ms   Deployment/example-ms   <unknown>/50%   1         1         1         33s


Replica Set Events:
NAME                              DESIRED   CURRENT   READY     AGE
example-ms-59c9b45565   1         1         0         1s
example-ms-76896c7f7f   1         1         1         2s
example-ms-59c9b45565   1         1         1         2s
example-ms-76896c7f7f   1         1         1         32s
example-ms-59c9b45565   1         1         1         32s
example-ms-76896c7f7f   0         1         1         32s
example-ms-76896c7f7f   0         1         1         32s
example-ms-76896c7f7f   0         0         0         32s

Pod Events:
NAME                                    READY     STATUS              RESTARTS   AGE
example-ms-59c9b45565-6b5v8   0/1       ContainerCreating   0         0s
example-ms-76896c7f7f-cth7x   1/1       Running   0         2s
example-ms-59c9b45565-6b5v8   1/1       Running   0         2s
example-ms-59c9b45565-d2k8w   0/1       Terminating   0         2m
example-ms-59c9b45565-d2k8w   0/1       Terminating   0         2m
example-ms-59c9b45565-d2k8w   0/1       Terminating   0         2m
example-ms-59c9b45565-d2k8w   0/1       Terminating   0         2m
example-ms-76896c7f7f-cth7x   1/1       Terminating   0         32s
example-ms-76896c7f7f-cth7x   0/1       Terminating   0         1m
example-ms-76896c7f7f-cth7x   0/1       Terminating   0         1m
example-ms-76896c7f7f-cth7x   0/1       Terminating   0         1m




Deployment Spec:
spec:
  minReadySeconds: 30
  progressDeadlineSeconds: 120
  replicas: 1
  revisionHistoryLimit: 15
  selector:



Deployment status:
tatus:
  availableReplicas: 1
  conditions:
  - lastTransitionTime: 2019-04-21T08:51:03Z
    lastUpdateTime: 2019-04-21T08:51:35Z
    message: ReplicaSet "example-ms-59c9b45565" has successfully progressed.
    reason: NewReplicaSetAvailable
    status: "True"
    type: Progressing
  - lastTransitionTime: 2019-04-21T16:53:02Z
    lastUpdateTime: 2019-04-21T16:53:02Z
    message: Deployment has minimum availability.
    reason: MinimumReplicasAvailable
    status: "True"
    type: Available
  observedGeneration: 3
  readyReplicas: 1
  replicas: 1
  updatedReplicas: 1