K8S環境安裝第三篇:安裝dashbord的那些坑
之前寫過兩篇這個K8S安裝的,但是還沒寫怎麼安裝dashbord視覺化頁面的。因為最近虛擬機器出了問題,導致又要重新安裝一遍。這裡就藉此完善下。
接下來我們在在master節點上部署k8s-dashboard元件,該元件為k8s的web ui元件:
1. 執行下面檔案內容 kubernetes-dashboard.yaml
kubectl apply -f kubernetes-dashboard.yaml
檔案內容如下:標記紅色的地方是特別需要留意的地方,避免不必要的問題
# Copyright 2017 The Kubernetes Authors.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# ------------------- Dashboard Secret ------------------- #
apiVersion: v1
kind: Secret
metadata:
labels:
k8s-app: kubernetes-dashboard
name: kubernetes-dashboard-certs
namespace: kube-system
type: Opaque
---
# ------------------- Dashboard Service Account ------------------- #
apiVersion: v1
kind: ServiceAccount
metadata:
labels:
k8s-app: kubernetes-dashboard
name: kubernetes-dashboard
namespace: kube-system
---
# ------------------- Dashboard Role & Role Binding ------------------- #
kind: Role
apiVersion: rbac.authorization.k8s.io/v1
metadata:
name: kubernetes-dashboard-minimal
namespace: kube-system
rules:
# Allow Dashboard to create 'kubernetes-dashboard-key-holder' secret.
- apiGroups: [""]
resources: ["secrets"]
verbs: ["create"]
# Allow Dashboard to create 'kubernetes-dashboard-settings' config map.
- apiGroups: [""]
resources: ["configmaps"]
verbs: ["create"]
# Allow Dashboard to get, update and delete Dashboard exclusive secrets.
- apiGroups: [""]
resources: ["secrets"]
resourceNames: ["kubernetes-dashboard-key-holder", "kubernetes-dashboard-certs"]
verbs: ["get", "update", "delete"]
# Allow Dashboard to get and update 'kubernetes-dashboard-settings' config map.
- apiGroups: [""]
resources: ["configmaps"]
resourceNames: ["kubernetes-dashboard-settings"]
verbs: ["get", "update"]
# Allow Dashboard to get metrics from heapster.
- apiGroups: [""]
resources: ["services"]
resourceNames: ["heapster"]
verbs: ["proxy"]
- apiGroups: [""]
resources: ["services/proxy"]
resourceNames: ["heapster", "http:heapster:", "https:heapster:"]
verbs: ["get"]
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
name: kubernetes-dashboard-minimal
namespace: kube-system
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: Role
name: kubernetes-dashboard-minimal
subjects:
- kind: ServiceAccount
name: kubernetes-dashboard
namespace: kube-system
---
# ------------------- Dashboard Deployment ------------------- #
kind: Deployment
apiVersion: apps/v1
metadata:
labels:
k8s-app: kubernetes-dashboard
name: kubernetes-dashboard
namespace: kube-system
spec:
replicas: 1
revisionHistoryLimit: 10
selector:
matchLabels:
k8s-app: kubernetes-dashboard
template:
metadata:
labels:
k8s-app: kubernetes-dashboard
spec:
containers:
- name: kubernetes-dashboard
image: registry.aliyuncs.com/google_containers/kubernetes-dashboard-amd64:v1.10.1
ports:
- containerPort: 8443
protocol: TCP
args:
- --auto-generate-certificates
# Uncomment the following line to manually specify Kubernetes API server Host
# If not specified, Dashboard will attempt to auto discover the API server and connect
# to it. Uncomment only if the default does not work.
# - --apiserver-host=http://my-address:port
volumeMounts:
- name: kubernetes-dashboard-certs
mountPath: /certs
# Create on-disk volume to store exec logs
- mountPath: /tmp
name: tmp-volume
livenessProbe:
httpGet:
scheme: HTTPS
path: /
port: 8443
initialDelaySeconds: 30
timeoutSeconds: 30
volumes:
- name: kubernetes-dashboard-certs
secret:
secretName: kubernetes-dashboard-certs
- name: tmp-volume
emptyDir: {}
serviceAccountName: kubernetes-dashboard
# Comment the following tolerations if Dashboard must not be deployed on master
tolerations:
- key: node-role.kubernetes.io/master
effect: NoSchedule
---
# ------------------- Dashboard Service ------------------- #
kind: Service
apiVersion: v1
metadata:
labels:
k8s-app: kubernetes-dashboard
name: kubernetes-dashboard
namespace: kube-system
spec:
type: NodePort
ports:
- port: 443
targetPort: 8443
nodePort:30001
selector:
k8s-app: kubernetes-dashboard
2.檢視訪問dashboard服務的埠號,訪問IP使用master節點的IP地址
[root@k8s-node1 dashboard-certs]# kubectl get svc kubernetes-dashboard -n kube-system
訪問連線:
https://192.168.56.100:30001/
3. 如何使用令牌登陸:
[root@k8s-node1]# kubectl create serviceaccount dashboard-admin -n kube-system [root@k8s-node1]# kubectl create clusterrolebinding dashboard-admin --clusterrole=cluster-admin --serviceaccount=kube-system:dashboard-admin
[root@k8s-node1 dashboard-certs]# kubectl get secret -n kube-system|grep dashboard
[root@k8s-node1 dashboard-certs]# kubectl describe secret dashboard-admin-token-7v2gn -n kube-system
最後登入的效果如下:
4. 其他可能問題
K8s叢集排錯,斷電重啟The connection to the server apiserver.k8s:6443 was refused - did you specify the right
解決方案
1.首先確保Swap 已經關閉
可以採用臨時關閉 swapoff -a 但是斷電重啟之後需要再次設定 也可以設定永久關閉
2各個節點之間防火牆 一定要檢查 systemctl stop firewalld
3.檢視kubelet 服務 是否正常systemctl status kubelet
4.如果一會又不正常了請看詳細資訊journalctl -xefu kubelet
5.如果發現Unit kubelet.service entered failed state.code=exited, status=255 說明這臺節點有汙點 ,將汙點刪除。
rm -rf /var/lib/kubelet/cpu_manager_state
6.排除問題之後 systemctl start kubelet 重啟完成
7.檢視node ,pod
kubectl get node
kubectl get pods --all-namespaces
kubernetes dashboard 的許可權錯誤
執行如下命令即可:
kubectl create clusterrolebinding kubernetes-dashboard --clusterrole=cluster-admin --serviceaccount=kube-system:kubernetes-dashboard
以上為主要內容。記錄一下,以後重新安裝不費勁。