Kubernetes ServiceAccount的配置

opo

　　May 24 08:07:09 k8s-master pulseaudio[3094]: [alsa-sink-Intel ICH] alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write!
　　May 24 08:07:09 k8s-master pulseaudio[3094]: [alsa-sink-Intel ICH] alsa-sink.c: Most likely this is a bug in the ALSA driver 'snd_intel8x0'. Please report this issue to the ALSA developers.
　　May 24 08:07:09 k8s-master pulseaudio[3094]: [alsa-sink-Intel ICH] alsa-sink.c: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
　　May 24 08:07:47 k8s-master systemd: Starting Kubernetes API Server...
　　May 24 08:07:47 k8s-master kube-apiserver: Flag --port has been deprecated, see --insecure-port instead.
　　May 24 08:07:47 k8s-master kube-apiserver: I0524 08:07:47.680379    4239 config.go:562] Will report 192.168.0.105 as public IP address.
　　May 24 08:07:47 k8s-master kube-apiserver: E0524 08:07:47.726082    4239 reflector.go:199] k8s.io/kubernetes/plugin/pkg/admission/resourcequota/resource_access.go:83: Failed to list *api.ResourceQuota: Get http://0.0.0.0:8080/api/v1/resourcequotas?resourceVersion=0: dial tcp 0.0.0.0:8080: getsockopt: connection refused
　　May 24 08:07:47 k8s-master kube-apiserver: E0524 08:07:47.726161    4239 reflector.go:199] k8s.io/kubernetes/plugin/pkg/admission/serviceaccount/admission.go:119: Failed to list *api.Secret: Get http://0.0.0.0:8080/api/v1/secrets?fieldSelector=type%3Dkubernetes.io%2Fservice-account-token&resourceVersion=0: dial tcp 0.0.0.0:8080: getsockopt: connection refused
　　May 24 08:07:47 k8s-master kube-apiserver: E0524 08:07:47.726207    4239 reflector.go:199] k8s.io/kubernetes/plugin/pkg/admission/serviceaccount/admission.go:103: Failed to list *api.ServiceAccount: Get http://0.0.0.0:8080/api/v1/serviceaccounts?resourceVersion=0: dial tcp 0.0.0.0:8080: getsockopt: connection refused
　　May 24 08:07:47 k8s-master kube-apiserver: [restful] 2017/05/24 08:07:47 log.go:30: [restful/swagger] listing is available at https://192.168.0.105:443/swaggerapi/
　　May 24 08:07:47 k8s-master kube-apiserver: [restful] 2017/05/24 08:07:47 log.go:30: [restful/swagger] https://192.168.0.105:443/swaggerui/ is mapped to folder /swagger-ui/
　　May 24 08:07:47 k8s-master kube-apiserver: E0524 08:07:47.902354    4239 reflector.go:199] pkg/controller/informers/factory.go:89: Failed to list *api.Namespace: Get http://0.0.0.0:8080/api/v1/namespaces?resourceVersion=0: dial tcp 0.0.0.0:8080: getsockopt: connection refused
　　May 24 08:07:47 k8s-master kube-apiserver: E0524 08:07:47.902419    4239 reflector.go:199] pkg/controller/informers/factory.go:89: Failed to list *api.LimitRange: Get http://0.0.0.0:8080/api/v1/limitranges?resourceVersion=0: dial tcp 0.0.0.0:8080: getsockopt: connection refused
　　May 24 08:07:47 k8s-master systemd: Started Kubernetes API Server.
　　May 24 08:07:47 k8s-master kube-apiserver: I0524 08:07:47.923462    4239 serve.go:95] Serving securely on 0.0.0.0:443
　　May 24 08:07:47 k8s-master kube-apiserver: I0524 08:07:47.923542    4239 serve.go:109] Serving insecurely on 0.0.0.0:8080
　　我对这个Failed to list *api.Secret的错误查了半天网上的材料想要消除,但后来看起来应该没有太大影响.
　　如果通过systemctl 启动不成功,可能尝试命令行启动.
　　APIServer和Controller Manager的命令行启动方式