k8s dashboard

dashboardkubernetes-dashboard-bbc7b8b5-rj8hf 1/1 Running 0 10m> kubectl get svc -n kube-system | grep dashboard kubernetes-dashboard ClusterIP 10.254.61.253 To access the dashboard from a local workstation, you must create a secure channel for your kubernetes cluster.Run the following command:

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:9090Initiald

clusterrolebinding kubelet-bootstrap--clusterrole=system:node-bootstrapper--user=kubelet-bootstrapFifth step: Start Kubelet on the node server, you can view the CSR certificate on MasterAfter the certificate is generated, you need to allow the certificateKUBECTL Certificate Approve certificate name (that is, the name value above)Then you can see the status of the cluster.KUBECTL Get nodeAt this point, the k8s cluster deployment is complete.Next, we'l

Create clusterrolebinding kubelet-bootstrap--clusterrole=system:node-bootstrapper--user=kubelet-bootstrap Fifth step: Start Kubelet on the node server, you can view the CSR certificate on Master After the certificate is generated, you need to allow the certificate KUBECTL Certificate Approve certificate name (that is, the name value above) Then you can see the status of the cluster.KUBECTL Get node At this point, the k8s cluster deployment is co

deploy_dashboard {if ${kubectl} Get Rc-l K8s-app=kubernetes-dashboard--namespace=kube-system | grep kubernetes-dashboard-v >/dev/null; Then echo "Kubernetes Dashboard Replicationcontroller already exists" else echo "Creating Kubernetes Dash Board Replicationcontroller "${kubectl} create-f ${kube_root}/cluster/addon

Create clusterrolebinding kubelet-bootstrap--clusterrole=system:node-bootstrapper--user=kubelet-bootstrap Fifth step: Start Kubelet on the node server, you can view the CSR certificate on Master After the certificate is generated, you need to allow the certificate KUBECTL Certificate Approve certificate name (that is, the name value above) Then you can see the status of the cluster.KUBECTL Get node At this point, the k8s cluster deployment is co

kubernetes Create the following script: VI auto_pull_images.sh Add the following content to the script: #! /Bin/bashimages = (kube-proxy-amd64: v1.12.1 kube-scheduler-amd64: v1.12.1 kube-controller-manager-amd64: v1.12.1 kube-apiserver-amd64: v1.12.1 etcd-amd64: 3.2.24 pause-amd64: 3.1 kubernetes-dashboard-amd64: v1.10.0 k8s-dns-sidecar-amd64: 1.14.8 k8s-dns-k

CentOS7 Build Kubernetes DashboardAn environmental statementCentos7 Three, master node one, node nodes twoDashboard requires a mirror and requires a command download:Docker Pull mritd/kubernetes-dashboard-amd64:v1.5.1PS: There are many other mirrors can also build dashboard, but this version is the Chinese version ofNote: All two node nodes need to download this image, the master node does not, because the

Using Kubeasz to install multi-master multi-slave k8s cluster One, Project introductionKubeasz for GitHub on the open source of a project for the installation of k8s cluster, there are many methods to install k8s, but more than single-master multi-node installation, but Kubeasz can be very convenient to achieve multi-master multi-from, for the experiment is reall

First, prerequisites1, first you will have ready-made kubernetes cluster, if you have nothing now, please refer to:http://zlyang.blog.51cto.com/1196234/19510102, the proposed use ETCD cluster, the construction process please refer to:http://zlyang.blog.51cto.com/1196234/1951164Ii. Deployment of Kubernetes-dashboard[All machines: Master, Node1, Node2]1, install flannel (Flannel for Management containers Network)[Email protected] ~]# yum-y install epel-

Cat > Kube-apiserver.service [k8s]k8s api-server start systemd parameter analysis

Kubectl Run Nginx--image=nginx--replicas=3[[email protected] ~]# Kubectl get pod-o WideNAME ready STATUS Restarts IP NODENGINX-8586CF59-C5QPW 1/1 Running 0 8m 172.17.96.2 192.168.56.12nginx-8586cf59-lm85p 1/1 Running 0 8m 172.17.2.2 192.168.56.11NGINX-8586CF59-N58BM 1/1 Running 0 8m 172.17.96.3 192.168.56.12[[email protected] ~]# kubectl get podNAME Ready STATUS RestartsNGINX-8586CF59-C5QPW 1/1 Running 0 8mnginx-8586cf59-lm85p 1/1 Running 0 8mNGINX-8586CF59-N58BM 1/1 Running 0 8m[Email protected

expected pod status is consistent with the current status, and the number of pods can be elastically scaled. This mainly ensures the normal operation of the dashboard;Create a kube-dashboard-rc.yaml file with the following content: apiVersion: v1kind: ReplicationControllermetadata:# Keep the name in sync with image version and# gce/coreos/kube-manifests/addons/dashboar