が不明な理由にKubernetes APIサーバーのデュオを開始できませんでしたサービスが開始されていないと、リスナーは、ここでポート8080</p> <p>上で活性化されていない

Question

私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-apiserver 1000年の/ var/log/messagesに

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 

-n -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. 

尾

Answer 1

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

使用している引数が有効ではないようです。

有効な引数のリストhereを確認してください。

Kubernetes The Hard Wayガイドに従って、APIサーバーを信頼できる方法で実行することもできます。