無法啓動Kubernetes API服務器二人未知的原因，

的服務沒有啓動，並偵聽器未在端口激活8080無法啓動Kubernetes API服務器二人未知的原因，

這裏是我的kubernetes配置：

KUBE_LOGTOSTDERR="--logtostderr=true" 
KUBE_LOG_LEVEL="--v=0" 
KUBE_ALLOW_PRIV="--allow-privileged=false" 
KUBE_MASTER="--master=http://centos-master:8080" 
KUBE_ETCD_SERVERS="--etcd-servers=http://centos-master:2379"

systemctl狀態KUBE-API服務器-l

● 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 Mon 2017-08-14 12:07:04 +0430; 29s ago 
    Docs: https://github.com/GoogleCloudPlatform/kubernetes 
    Process: 2087 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: 2087 (code=exited, status=2) 

Aug 14 12:07:04 centos-master systemd[1]: kube-apiserver.service: main process exited, code=exited, status=2/INVALIDARGUMENT 
Aug 14 12:07:04 centos-master systemd[1]: Failed to start Kubernetes API Server. 
Aug 14 12:07:04 centos-master systemd[1]: Unit kube-apiserver.service entered failed state. 
Aug 14 12:07:04 centos-master systemd[1]: kube-apiserver.service failed. 
Aug 14 12:07:04 centos-master systemd[1]: kube-apiserver.service holdoff time over, scheduling restart. 
Aug 14 12:07:04 centos-master systemd[1]: start request repeated too quickly for kube-apiserver.service 
Aug 14 12:07:04 centos-master systemd[1]: Failed to start Kubernetes API Server. 
Aug 14 12:07:04 centos-master systemd[1]: Unit kube-apiserver.service entered failed state. 
Aug 14 12:07:04 centos-master systemd[1]: kube-apiserver.service failed.

尾-n 1000的/ var /日誌/消息

resourceVersion=0: dial tcp 10.0.2.4:8080: getsockopt: connection refused 
Aug 14 12:12:30 centos-master kube-scheduler: E0814 12:12:30.240160  606 reflector.go:199] k8s.io/kubernetes/plugin/pkg/scheduler/factory/factory.go:466: Failed to list *api.PersistentVolume: Get http://centos-master:8080/api/v1/persistentvolumes?resourceVersion=0: dial tcp 10.0.2.4:8080: getsockopt: connection refused 
Aug 14 12:12:30 centos-master kube-scheduler: E0814 12:12:30.242039  606 reflector.go:199] k8s.io/kubernetes/plugin/pkg/scheduler/factory/factory.go:470: Failed to list *api.Service: Get http://centos-master:8080/api/v1/services?resourceVersion=0: dial tcp 10.0.2.4:8080: getsockopt: connection refused 
Aug 14 12:12:30 centos-master kube-scheduler: E0814 12:12:30.242924  606 reflector.go:199] k8s.io/kubernetes/plugin/pkg/scheduler/factory/factory.go:457: Failed to list *api.Pod: Get http://centos-master:8080/api/v1/pods?fieldSelector=spec.nodeName%3D%2Cstatus.phase%21%3DFailed%2Cstatus.phase%21%3DSucceeded&resourceVersion=0: dial tcp 10.0.2.4:8080: getsockopt: connection refused 
Aug 14 12:12:30 centos-master kube-scheduler: E0814 12:12:30.269386  606 reflector.go:199] k8s.io/kubernetes/plugin/pkg/scheduler/factory/factory.go:473: Failed to list *api.ReplicationController: Get http://centos-master:8080/api/v1/replicationcontrollers?resourceVersion=0: dial tcp 10.0.2.4:8080: getsockopt: connection refused 
Aug 14 12:12:30 centos-master kube-scheduler: E0814 12:12:30.285782  606 reflector.go:199] k8s.io/kubernetes/plugin/pkg/scheduler/factory/factory.go:481: Failed to list *extensions.ReplicaSet: Get http://centos-master:8080/apis/extensions/v1beta1/replicasets?resourceVersion=0: dial tcp 10.0.2.4:8080: getsockopt: connection refused 
Aug 14 12:12:30 centos-master kube-scheduler: E0814 12:12:30.286529  606 reflector.go:199] pkg/controller/informers/factory.go:89: Failed to list *api.PersistentVolumeClaim: Get http://centos-master:8080/api/v1/persistentvolumeclaims?resourceVersion=0: dial tcp 10.0.2.4:8080: getsockopt: connection refused

來源

2017-08-14 Mojtaba Al

firewalld被禁用，ETCD_LISTEN_CLIENT_URLS =「http://0.0.0.0:2379」，ETCD_ADVERTISE_CLIENT_URLS =「http://0.0.0.0:2379」，我的環境是4個運行在本地nat的虛擬機以及它們的本地nat基本網絡框 –

你用什麼版本？您可以使用'kubeadm'命令來配置您的羣集。 – sfgroups

'kubeadm'是新工具，它負責配置主節點。它易於使用。 – sfgroups

systemd[1]: kube-apiserver.service: main process exited, code=exited, status=2/INVALIDARGUMENT

您使用的參數似乎不正確。

檢查有效參數列表here。

您也可以按照Kubernetes The Hard Way指南中的信任方式運行API服務器。

來源

2017-08-14 10:49:36

無法啓動Kubernetes API服務器二人未知的原因，

回答

相關問題