Kubernetes1.91 (k8s) Installation deployment Process (eight)--Kubernetes-dashboard installation

Kubernets-dashboard as the name implies is the operation panel installation, that is, the visual management machine, agreed that we use the image with the configuration file deployment.

1. Download Image:

Docker pull Registry.docker-cn.com/kubernetesdashboarddev/kubernetes-dashboard-amd64:head

2. New deployment Configuration file

2 files required.

Document One Dashboard.yaml:

apiVersion:v1kind:ServiceAccountmetadata:name:kubernetes-Dashboard Namespace:kube-system---ApiVersion:rbac.authorization.k8s.io/v1beta1kind:ClusterRoleBindingmetadata:name:kubernetes-Dashboard labels:k8s-app:kubernetes-DashboardroleRef:apiGroup:rbac.authorization.k8s.io kind:clusterrole Name:cluster-adminsubjects:-Kind:serviceaccount name:kubernetes-Dashboard Namespace:kube-system---apiversion:extensions/v1beta1kind:Deploymentmetadata:name:kubernetes-Dashboard Namespace:kube-system labels:k8s-app:kubernetes-Dashboard Kubernetes.io/cluster-service:"true"Addonmanager.kubernetes.io/mode:Reconcilespec:selector:matchLabels:k8s-app:kubernetes-Dashboard template:metadata:labels:k8s-app:kubernetes-Dashboard Annotations:scheduler.alpha.kubernetes.io/critical-pod:"'spec:serviceAccountName:kubernetes-Dashboard Containers:-name:kubernetes-Dashboard Image:registry.docker-cn.com/kubernetesdashboarddev/kubernetes-dashboard-amd64:headresources:limits:cpu:100m memory:300mi requests:cpu:1 00m memory:100mi Ports:-Containerport:9090LivenessProbe:httpGet:path:/Port:9090Initialdelayseconds: -timeoutseconds: -tolerations:-Key:"criticaladdonsonly"Operator:"Exists"

Document Two:

Dashboard-svc.yaml file

apiVersion:v1kind:Servicemetadata:  name:kubernetes-dashboard  namespace:kube-  System  Labels:    k8s-app:kubernetes-dashboard    kubernetes.io"true "     addonmanager.kubernetes.io/mode:reconcilespec:  selector:    k8s-app: kubernetes-Dashboard  type:nodeport  ports:  9090    9090 32017      

3. Execute 2 Deployment files respectively

KUBECTL Create-f Dashboard-svc.yaml

4. Enquiry Service

As with the previous session, replace the shut-down machine.

5, how to access?

Careful people should change the law our Yaml file has a ports definition, we define a nodeport way, the port is 32017, so

32017 on the host, we can use the host ip+32017, that is, 10.10.90.105:32017 access,

Now you can use the panel to manage the cluster, but the panel does not show a certain load of node nodes, such as CPU, memory, etc., we can follow another Heapster plugin in the next section to display, the next tutorial goodbye!

Kubernetes1.91 (k8s) Installation deployment Process (eight)--Kubernetes-dashboard installation