规模为1的部署有两个吊舱

Question

我有一个scale=1部署，但当我运行get吊舱时，我有2/2.当我把部署扩展到0，而不是1时，我又得到了2个吊舱.这怎麽可能？正如我在下面看到的，prometeus有2：

PS C:\dev\> kubectl.exe get pods -n monitoring
NAME                                             READY   STATUS    RESTARTS   AGE
grafana-6c79d58dd-5k8cs                          1/1     Running   0          3d21h
prometheus-alertmanager-5584c7b8d-k7zrn          2/2     Running   0          3d21h
prometheus-kube-state-metrics-6b46f67bf6-kt5dq   1/1     Running   0          3d21h
prometheus-node-exporter-fj5zv                   1/1     Running   0          3d21h
prometheus-node-exporter-vgjtt                   1/1     Running   0          3d21h
prometheus-node-exporter-xfm5h                   1/1     Running   0          3d21h
prometheus-node-exporter-zp9mw                   1/1     Running   0          3d21h
prometheus-pushgateway-6c9764ff46-s295t          1/1     Running   0          3d21h
prometheus-server-b647558d5-jxgtl                2/2     Running   0          2m18s

部署如下：

PS C:\dev> kubectl.exe describe deployment prometheus-server -n monitoring
Name:                   prometheus-server
Namespace:              monitoring
CreationTimestamp:      Thu, 16 Jul 2020 11:46:58 +0300
Labels:                 app=prometheus
                        app.kubernetes.io/managed-by=Helm
                        chart=prometheus-11.7.0
                        component=server
                        heritage=Helm
                        release=prometheus
Annotations:            deployment.kubernetes.io/revision: 1
                        meta.helm.sh/release-name: prometheus
                        meta.helm.sh/release-namespace: monitoring
Selector:               app=prometheus,component=server,release=prometheus
Replicas:               1 desired | 1 updated | 1 total | 1 available | 0 unavailable
StrategyType:           RollingUpdate
MinReadySeconds:        0
RollingUpdateStrategy:  25% max unavailable, 25% max surge
Pod Template:
  Labels:           app=prometheus
                    chart=prometheus-11.7.0
                    component=server
                    heritage=Helm
                    release=prometheus
  Service Account:  prometheus-server
  Containers:
   prometheus-server-configmap-reload:
    Image:      jimmidyson/configmap-reload:v0.3.0
    Port:       <none>
    Host Port:  <none>
    Args:
      --volume-dir=/etc/config
      --webhook-url=http://127.0.0.1:9090/-/reload
    Environment:  <none>
    Mounts:
      /etc/config from config-volume (ro)
   prometheus-server:
    Image:      prom/prometheus:v2.19.0
    Port:       9090/TCP
    Host Port:  0/TCP
    Args:
      --storage.tsdb.retention.time=15d
      --config.file=/etc/config/prometheus.yml
      --storage.tsdb.path=/data
      --web.console.libraries=/etc/prometheus/console_libraries
      --web.console.templates=/etc/prometheus/consoles
      --web.enable-lifecycle
    Liveness:     http-get http://:9090/-/healthy delay=30s timeout=30s period=15s #success=1 #failure=3
    Readiness:    http-get http://:9090/-/ready delay=30s timeout=30s period=5s #success=1 #failure=3
    Environment:  <none>
    Mounts:
      /data from storage-volume (rw)
      /etc/config from config-volume (rw)
  Volumes:
   config-volume:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      prometheus-server
    Optional:  false
   storage-volume:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  prometheus-server
    ReadOnly:   false
Conditions:
  Type           Status  Reason
  ----           ------  ------
  Progressing    True    NewReplicaSetAvailable
  Available      True    MinimumReplicasAvailable
OldReplicaSets:  prometheus-server-b647558d5 (1/1 replicas created)
NewReplicaSet:   <none>
Events:
  Type    Reason             Age    From                   Message
  ----    ------             ----   ----                   -------
  Normal  ScalingReplicaSet  5m32s  deployment-controller  Scaled down replica set prometheus-server-b647558d5 to 0
  Normal  ScalingReplicaSet  5m14s  deployment-controller  Scaled up replica set prometheus-server-b647558d5 to 1

奇怪的是，正如上面所示，k8s认为它是1脚，如果看起来像是人工操作。我不知道现在是什么

Answer 1

两个容器一个吊舱。您也可以在描述输出中看到它们都列在Containers:下面。一种是Prometheus本身，另一种是当配置文件更改时触发重新加载的sidecar，因为Prometheus本身不这样做。