Kubernetes 谁启动kube apiserver以及如何配置其启动参数？

kube apiserver是由kubeadm init创建的我的配置中的containerd.service启动的，如何检查containerd.service的配置以及它如何知道如何启动kube apiserver

ytong@controller-4135505:~$ systemctl status containerd.service
● containerd.service - containerd container runtime
   Loaded: loaded (/lib/systemd/system/containerd.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2020-06-09 04:34:04 GMT+7; 3min 24s ago
     Docs: https://containerd.io
  Process: 5135 ExecStartPre=/sbin/modprobe overlay (code=exited, status=0/SUCCESS)
 Main PID: 5138 (containerd)
    Tasks: 228
   CGroup: /system.slice/containerd.service
           ├─5138 /usr/bin/containerd
           ├─5821 etcd --advertise-client-urls=https://10.169.97.0:2379 --cert-file=/etc/kubernetes/pki/etcd/server.crt --client-cert-auth=true --data-dir=/var/lib/etcd --initial-advertise-
           ├─5847 kube-scheduler --authentication-kubeconfig=/etc/kubernetes/scheduler.conf --authorization-kubeconfig=/etc/kubernetes/scheduler.conf --bind-address=127.0.0.1 --kubeconfig=/
         * ├─5868 kube-apiserver --advertise-address=10.169.97.0 --allow-privileged=true --authorization-mode=Node,RBAC --client-ca-file=/etc/kubernetes/pki/ca.crt --enable-admission-plugin
           └─7587 kube-controller-manager --authentication-kubeconfig=/etc/kubernetes/controller-manager.conf --authorization-kubeconfig=/etc/kubernetes/controller-manager.conf --bind-addre```
And it is not controlled by kubelet.service right since I restart kubelet.service will not restart kube-apiserver daemon.

The only configuration file found by me for containerd.service is for /lib/systemd/system/containerd.service, but it only tell the execStart is /usr/bin/containerd.

The /usr/bin/containerd is a binary and all clues are ended here for me to find how it can find kube-apiserver to start.

Or does containerd has some path to hold its configuration files?

---

Kube API服务器从位于

/etc/kubernetes/manifests/Kube apiserver的yaml启动。yaml

您可以编辑yaml以添加或删除启动参数。Kubelet知道在该路径中查找任何yaml，如果存在任何yaml，Kubelet将把容器创建委托给containerd。所以containerd并不直接了解KubernetesAPI服务器。对于ContainerDkubernetesAPI服务器只是另一个要启动的容器

---

Kube API服务器从位于

/etc/kubernetes/manifests/Kube apiserver的yaml启动。yaml

您可以编辑yaml以添加或删除启动参数。Kubelet知道在该路径中查找任何yaml，如果存在任何yaml，Kubelet将把容器创建委托给containerd。所以containerd并不直接了解KubernetesAPI服务器。对于ContainerDkubernetesAPI服务器只是另一个要启动的容器

---

是的，你说得对。kube apiserver与etcd、kube调度程序、kube控制器管理器一起作为静态pod启动，并由kubelet进行精确管理。是的，您是对的。kube apiserver与etcd、kube调度程序、kube控制器管理器一起作为静态pod启动，并由kubelet精确管理。