部署Kubernetes kube-apiserver启动失败-蒲公英云

部署Kubernetes kube-apiserver启动失败

女爷i 2022-02-02 14:25 1301阅读 0赞

systemctl restart kube-apiserver启动失败

[root@centos-master yum.repos.d]# systemctl status kube-apiserver.service
● kube-apiserver.service - Kubernetes API Server
   Loaded: loaded (/usr/lib/systemd/system/kube-apiserver.service; enabled; vendor preset: disabled)
   Active: failed (Result: start-limit) since 六 2019-05-11 18:33:33 CST; 8min ago
     Docs: https://github.com/GoogleCloudPlatform/kubernetes
  Process: 3661 ExecStart=/usr/bin/kube-apiserver $KUBE_LOGTOSTDERR $KUBE_LOG_LEVEL $KUBE_ETCD_SERVERS $KUBE_API_ADDRESS $KUBE_API_PORT $KUBELET_PORT $KUBE_ALLOW_PRIV $KUBE_SERVICE_ADDRESSES $KUBE_ADMISSION_CONTROL $KUBE_API_ARGS (code=exited, status=2)
 Main PID: 3661 (code=exited, status=2)
5月 11 18:33:33 centos-master systemd[1]: kube-apiserver.service: main process exited, code=exited, status=2/INVALIDARGUMENT
5月 11 18:33:33 centos-master systemd[1]: Failed to start Kubernetes API Server.
5月 11 18:33:33 centos-master systemd[1]: Unit kube-apiserver.service entered failed state.
5月 11 18:33:33 centos-master systemd[1]: kube-apiserver.service failed.
5月 11 18:33:33 centos-master systemd[1]: kube-apiserver.service holdoff time over, scheduling restart.
5月 11 18:33:33 centos-master systemd[1]: start request repeated too quickly for kube-apiserver.service
5月 11 18:33:33 centos-master systemd[1]: Failed to start Kubernetes API Server.
5月 11 18:33:33 centos-master systemd[1]: Unit kube-apiserver.service entered failed state.
5月 11 18:33:33 centos-master systemd[1]: kube-apiserver.service failed.

当看到有这个提示的时候“ExecStart=/usr/bin/kube-apiserver $KUBE_LOGTOSTDERR $KUBE_LOG_LEVEL $KUBE_ETCD_SERVERS $KUBE_API_ADDRESS $KUBE_API_PORT $KUBELET_PORT $KUBE_ALLOW_PRIV $KUBE_SERVICE_ADDRESSES $KUBE_ADMISSION_CONTROL $KUBE_API_ARGS (code=exited, status=2)”，应该就能猜出是配置参数哪里有问题了

参考这个文章，debug测试
https://mp.csdn.net/mdeditor/90116634#
挖出命令并补全（参数在这两个文件/etc/kubernetes/config和/etc/kubernetes/apiserver）：

/usr/bin/kube-apiserver --logtostderr=true --v=0 --etcd-servers=http://127.0.0.1:2379 --address=0.0.0.0 -–port=8080 –kubelet_port=10250 allow-privileged=false -–service-cluster-ip-range=10.254.0.0/16 --admission-control=NamespaceLifecycle,NamespaceExists,LimitRanger,SecurityContextDeny,ServiceAccount,ResouceQuota