Kubernetes 1.5 Configuration Dashboard

Configuring the Kubernetes dashboard is relatively straightforward. Similarly, only need to obtain the Dashboard-controller.yaml and Dashboard-service.yaml files from the source code, slightly modify can:

wget Https://rawgit.com/kubernetes/kubernetes/master/cluster/addons/dashboard/dashboard-controller.yamlwget Https://rawgit.com/kubernetes/kubernetes/master/cluster/addons/dashboard/dashboard-service.yaml

Modify the Dashboard-controller.yaml as follows:grafana smtp configuration kubernetes

650) this.width=650; "src="/img/fz.gif "alt=" Copy Code "/>

/-----/tolerations: |::::-name:kubernetes--Containerport:/

650) this.width=650; "src="/img/fz.gif "alt=" Copy Code "/>

Dashboard-service.yaml do not need to modify, here directly to the source of the sample files:kubernetes pod configuration file

650) this.width=650; "src="/img/fz.gif "alt=" Copy Code "/>

Kind:serviceapiversion:v1metadata:labels:app:kubernetes-dashboard Name:kubernetes-dashboard Namespace:kube-sy Stemspec:type:NodePort ports:-port:80 targetport:9090 Selector:app:kubernetes-dashboard

650) this.width=650; "src="/img/fz.gif "alt=" Copy Code "/>

To perform a startup:

Kubectl create-f dashboard-controller.yamlkubectl create-f Dashboard-service.yaml pod configuration kubernetes

Once started, you can view the nodeport of the map by following these instructions:configure docker registry in kubernetes

[[email protected] kubernetes]# kubectl Get svc--namespace=kube-systemname cluster-ip External-ip PORT (S) agekube-dns 10.254.0.100 <none> 53/udp,53/tcp 5hkubernetes-dashboard 10. 254.68.60 <nodes> 80:30097/tcp 1d

The following access addresses are available for access:

http://10.5.10.116:8080/uihttp://10.5.10.116:30097

Dashboard interface configure kubernetes

650) this.width=650; "src=" Http://images2015.cnblogs.com/blog/788294/201703/788294-20170315174314885-386438656.png "/>

Error Description:kubernetes application configuration

During the actual configuration process, it was found that dashboard could not be started, and the pod log was viewed through KUBECTL logs as follows:

Using HTTP Port:9090error While initializing connection to Kubernetes Apiserver. This likely means, the cluster is Misconfigurhas invalid apiserver certificates or service accounts configuration ) or the--apiserver-host param points to a ser is not exist. Reason:invalid configuration:no configuration has been providedrefer to the troubleshooting guide for more information: Https://github.com/kubernetes/dashboard/blob/master/docs/uubleshooting.md

This error is due to the need to add the following parameters to the dashboard startup args parameter:

--apiserver-host=http://10.5.10.116:8080

In addition, we found that this dashboard visit does not have any authentication and authorization mechanism, and the follow-up will be dedicated to Kubernetes certification mechanism to do the relevant instructions.configuration management kubernetes

This article is from the "My Sky" blog, so be sure to keep this source http://sky66.blog.51cto.com/2439074/1933997

Kubernetes 1.5 Configuration Dashboard