Merge pull request #41521 from my-git9/path-27993

[zh-cn] sync setup-ha-etcd-with-kubeadm change-runtime-containerd configure-aggregation-layer

Author: k8s-ci-robot

content/zh-cn/docs/setup/production-environment/tools/kubeadm/setup-ha-etcd-with-kubeadm.md

@@ -125,7 +125,7 @@ on Kubernetes dual-stack support see [Dual-stack support with kubeadm](/docs/set
    # 将下面的 "systemd" 替换为你的容器运行时所使用的 cgroup 驱动。
    # kubelet 的默认值为 "cgroupfs"。
    # 如果需要的话，将 "--container-runtime-endpoint " 的值替换为一个不同的容器运行时。
-   ExecStart=/usr/bin/kubelet --address=127.0.0.1 --pod-manifest-path=/etc/kubernetes/manifests --cgroup-driver=systemd --container-runtime=remote --container-runtime-endpoint=unix:///var/run/containerd/containerd.sock
+   ExecStart=/usr/bin/kubelet --address=127.0.0.1 --pod-manifest-path=/etc/kubernetes/manifests --cgroup-driver=systemd --container-runtime-endpoint=unix:///var/run/containerd/containerd.sock
    Restart=always
    EOF
 

content/zh-cn/docs/tasks/administer-cluster/migrating-from-dockershim/change-runtime-containerd.md

@@ -157,14 +157,12 @@ then run the following commands:
 <!--
 ## Configure the kubelet to use containerd as its container runtime
 
-Edit the file `/var/lib/kubelet/kubeadm-flags.env` and add the containerd runtime to the flags.
-`--container-runtime=remote` and
+Edit the file `/var/lib/kubelet/kubeadm-flags.env` and add the containerd runtime to the flags;
 `--container-runtime-endpoint=unix:///run/containerd/containerd.sock`.
 -->
 ## 配置 kubelet 使用 containerd 作为其容器运行时
 
-编辑文件 `/var/lib/kubelet/kubeadm-flags.env`，将 containerd 运行时添加到标志中：
-`--container-runtime=remote` 和
+编辑文件 `/var/lib/kubelet/kubeadm-flags.env`，将 containerd 运行时添加到标志中；
 `--container-runtime-endpoint=unix:///run/containerd/containerd.sock`。
 
 <!--

content/zh-cn/docs/tasks/extend-kubernetes/configure-aggregation-layer.md

@@ -83,7 +83,7 @@ The rest of this section describes these steps in detail.
 
 The flow can be seen in the following diagram.
 
-![aggregation auth flows](/images/docs/aggregation-api-auth-flow.png).
+![aggregation auth flows](/images/docs/aggregation-api-auth-flow.png)
 
 The source for the above swimlanes can be found in the source of this document.
 -->