k8s v-1.20版本部署詳細程序[實測可用無坑]
1.部署環境準備
1.1 各軟體版本
| 系統 | Docker | k8s |
|---|---|---|
| Linux master 3.10.0-1160.el7.x86_64 | Docker version 20.10.17 | 1.20.0-0 |
1.2.部署規劃[單master]
| 主機名 | IP地址 | 角色 |
|---|---|---|
| k8s-master | 192.168.56.202 | master節點 |
| k8s-node1 | 192.168.56.203 | node節點 |
| k8s-node2 | 192.168.56.204 | node節點 |
2.系統環境的初始化操作
2.1 關閉防火墻
[root@K8sMaster ~]# systemctl stop firewalld
[root@K8sMaster ~]# systemctl disable firewalld
2.2 關閉selinux
#臨時關閉
[root@K8sMaster ~]# setenforce 0
#永久關閉
[root@K8sMaster ~]# sed -i 's/enforcing/disabled/' /etc/selinux/config 禁用
2.3 關閉swap交換磁區
#此處一定要關閉交換磁區否則在kubeadm初始化時會報錯
#臨時關閉
[root@K8sMaster ~]# swapoff -a
#永久關閉
[root@K8sMaster ~]# sed -ri 's/.*swap.*/#&/' /etc/fstab
2.4 設定主機名
#臨時處理
[root@K8sMaster ~]# hostnamectl set-hostname k8s-master
#永久處理
[root@master kubelet]# cat > /etc/hostname << EOF
k8smaster
EOF
2.5 設定主機名通信
[root@K8sMaster ~]# cat >> /etc/hosts << EOF
192.168.56.202 K8sMaster
192.168.56.203 K8sNode1
192.168.56.204 K8sNode2
EOF
2.6 橋接的IPv4流量傳遞到IpTABLES鏈
[root@K8sMaster sysctl.d]# cat > /etc/sysctl.d/k8s.conf << EOF
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1
net.ipv4.ip_forward = 1
EOF
# 配置生效
[root@K8sMaster ~]# sysctl --system
[root@K8sMaster ~]# sysctl -a
2.7 設定時鐘同步
[root@K8sMaster ~]# yum -y install ntpdate
# 從阿里云同步時鐘
[root@K8sMaster ~]# ntpdate time1.aliyun.com
3.安裝docker
3.1 設定docker倉庫
[root@K8sMaster ~]# yum install -y yum-utils
[root@K8sMaster ~]# yum-config-manager \
--add-repo \
https://download.docker.com/linux/centos/docker-ce.repo
[root@K8sMaster ~]# yum-config-manager \
--add-repo http://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo
3.2 安裝docker
# 安裝
[root@K8sMaster ~]# yum install docker-ce
# 啟用
[root@K8sMaster ~]# systemctl start docker
# 設定開機啟用 此處要設定開機啟動否則后面初始化時也會出錯
[root@K8sMaster ~]# systemctl enable docker
3.3 設定docker鏡像加速
[root@K8sMaster ~]# mkdir -p /etc/docker
[root@K8sMaster ~]# cat > /etc/docker/daemon.json << EOF
{
"registry-mirrors": ["https://49qrnx21.mirror.aliyuncs.com"]
}
EOF
[root@K8sMaster ~]# systemctl daemon-reload && systemctl restart docker
4. 使用kubeadm方式安裝k8s
4.1 設定K8S的倉庫
[root@K8sMaster ~]# cat > /etc/yum.repos.d/kubernetes.repo <<EOF
[kubernetes]
name=Kubernetes
baseurl=https://mirrors.aliyun.com/kubernetes/yum/repos/kubernetes-el7-x86_64/
enabled=1
gpgcheck=0
repo_gpgcheck=0
gpgkey=https://mirrors.aliyun.com/kubernetes/yum/doc/yum-key.gpg
EOF
4.2 安裝kubeadm kubectl kubelet
[root@K8sMaster ~]# yum install -y kubelet-1.20.0 kubeadm-1.20.0 kubectl-1.20.0
[root@K8sMaster ~]# systemctl enable kubelet
4.3 初始化kubeadm
【master節點,這一步只在master節點運行】
[root@K8sMaster ~]# kubeadm init \
--apiserver-advertise-address=192.168.56.202 \
--image-repository registry.aliyuncs.com/google_containers \
--kubernetes-version 1.20.0 \
--service-cidr=10.96.0.0/12 \
--pod-network-cidr=10.244.0.0/16
# 初始化完成之后會出現 如下字樣
Your Kubernetes control-plane has initialized successfully
.......
# 根據上述指示創建檔案
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config
# 并且出現 kubeadm join的提示 【此處的命令為node節點加入master的命令】
4.4 將node節點加入到 cluster集群
# 第一種情況在 master 節點 初始化完成之后會出現 加入集群的命令直接使用
# 第二種情況在部署node節點時候 token過期或者忘記 并且沒有--discovery-token-ca-cert-hash值
# 則需要在master主機重新生成 token 和 --discovery-token-ca-cert-hash
4.4.1 查看token狀態
[root@K8sMaster ~]# kubeadm token list
TOKEN TTL EXPIRES USAGES DESCRIPTION EXTRA GROUPS
hkqc00.c0sn7s5mpauw11fx 3h 2022-08-22T21:25:46+08:00 authentication,signing The default bootstrap token generated by 'kubeadm init'. system:bootstrappers:kubeadm:default-node-token
qlhylz.emm864nueu1ypv6p 23h 2022-08-23T17:44:21+08:00 authentication,signing <none> system:bootstrappers:kubeadm:default-node-token
xnwbbo.1ylplt1jrz10ms1u 23h 2022-08-23T17:44:27+08:00 authentication,signing <none> system:bootstrappers:kubeadm:default-node-token
4.4.2 生成新的token
[root@K8sMaster ~]# kubeadm token create
4.4.3 獲取--discovery-token-ca-cert-hash值
[root@K8sMaster ~]# openssl x509 -pubkey -in /etc/kubernetes/pki/ca.crt | openssl rsa -pubin -outform der 2>/dev/null | \
openssl dgst -sha256 -hex | sed 's/^.* //'
4.5 node節點加入master 集群
[root@K8sMaster ~]# kubeadm join 192.168.56.203:6443 --token qlhylz.emm864nueu1ypv6p \
--discovery-token-ca-cert-hash sha256:cd778ad01bdbc656eaff7d3b1273691f0070ebbadd2f1b8a3189a6dc1e88f39f
# 這里的兩個值使用剛才生成的值
4.6 查看節點狀態
[root@K8sMaster ~]# kubectl get nodes
NAME STATUS ROLES AGE VERSION
K8sMaster NotReady control-plane,master 20h v1.20.0
K8sNode1 NotReady <none> 13m v1.20.0
[root@K8sMaster ~]#
5.部署容器網路插件[CNI]
5.1 flannel網路插件的部署
kubectl apply -f https://raw.githubusercontent.com/flannel-io/flannel/master/Documentation/kube-flannel.yml
5.2 查看是否部署完成
[root@master ~]# kubectl get pods --all-namespaces
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-flannel kube-flannel-ds-c66ds 1/1 Running 0 14m
kube-flannel kube-flannel-ds-pxhzc 1/1 Running 0 14m
kube-system coredns-7f89b7bc75-gpgl9 1/1 Running 0 27h
kube-system coredns-7f89b7bc75-sr5mx 1/1 Running 0 27h
kube-system etcd-master 1/1 Running 2 27h
kube-system kube-apiserver-master 1/1 Running 2 27h
kube-system kube-controller-manager-master 1/1 Running 2 27h
kube-system kube-proxy-hkmd9 1/1 Running 0 7h33m
kube-system kube-proxy-mrxwf 1/1 Running 3 27h
kube-system kube-scheduler-master 1/1 Running 3 27h
5.3 查看node狀態
都是Ready狀態
[root@master ~]# kubectl get node
NAME STATUS ROLES AGE VERSION
master Ready control-plane,master 27h v1.20.0
node1 Ready <none> 7h31m v1.20.0
5.4 測驗集群
# 創建nginx應用
[root@master opt]# kubectl create deployment nginx --image=nginx
# 查看是否下載完成
[root@master opt]# kubectl get pods
NAME READY STATUS RESTARTS AGE
nginx-6799fc88d8-lx9nc 1/1 Running 0 3m44s
# 暴露埠
[root@master opt]# kubectl expose deployment nginx --port=80 --type=NodePort
# 查看埠情況
[root@master opt]# kubectl get pod,svc
NAME READY STATUS RESTARTS AGE
pod/nginx-6799fc88d8-lx9nc 1/1 Running 0 4m27s
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 28h
service/nginx NodePort 10.100.68.38 <none> 80:30572/TCP 3s
5.5 訪問測驗
訪問任意一個node節點的http://ip:30572 查看訪問結果 能訪問到nginx初始界面幾位成功
6. 安裝DashBoard面板
6.1下載Dashboard組態檔
[root@master opt]# wget https://raw.githubusercontent.com/kubernetes/dashboard/master/src/deploy/recommended/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.
# Configuration to deploy release version of the Dashboard UI compatible with
# Kubernetes 1.8.
#
# Example usage: kubectl create -f <this_file>
# ------------------- 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.cn-beijing.aliyuncs.com/minminmsn/kubernetes-dashboard: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
6.1 創建dashboard
[root@master opt]# kubectl apply -f kubernetes-dashboard.yaml
6.2 查看新建狀態
[root@master opt]# kubectl get pods --namespace=kube-system
NAME READY STATUS RESTARTS AGE
coredns-7f89b7bc75-gpgl9 1/1 Running 0 33h
coredns-7f89b7bc75-sr5mx 1/1 Running 0 33h
etcd-master 1/1 Running 2 33h
kube-apiserver-master 1/1 Running 2 33h
kube-controller-manager-master 1/1 Running 2 33h
kube-proxy-hkmd9 1/1 Running 0 13h
kube-proxy-mrxwf 1/1 Running 3 33h
kube-scheduler-master 1/1 Running 3 33h
kubernetes-dashboard-97c4799d9-4jp7k 1/1 Running 0 13m
6.3查看映射埠
[root@master opt]# kubectl get services kubernetes-dashboard -n kube-system
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kubernetes-dashboard NodePort 10.108.118.239 <none> 443:30001/TCP 4h39m
6.4 查看被分配的node
[root@master opt]# kubectl get pods -o wide --namespace=kube-system
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
coredns-7f89b7bc75-gpgl9 1/1 Running 0 33h 10.244.1.3 node1 <none> <none>
coredns-7f89b7bc75-sr5mx 1/1 Running 0 33h 10.244.1.2 node1 <none> <none>
etcd-master 1/1 Running 2 33h 192.168.56.202 master <none> <none>
kube-apiserver-master 1/1 Running 2 33h 192.168.56.202 master <none> <none>
kube-controller-manager-master 1/1 Running 2 33h 192.168.56.202 master <none> <none>
kube-proxy-hkmd9 1/1 Running 0 13h 192.168.56.203 node1 <none> <none>
kube-proxy-mrxwf 1/1 Running 3 33h 192.168.56.202 master <none> <none>
kube-scheduler-master 1/1 Running 3 33h 192.168.56.202 master <none> <none>
kubernetes-dashboard-97c4799d9-4jp7k 1/1 Running 0 16m 10.244.1.6 node1 <none> <none>
[root@master opt]#
6.5查看集群權限物件
[root@master opt]# kubectl get clusterroles
NAME CREATED AT
admin 2022-08-21T13:25:44Z
cluster-admin 2022-08-21T13:25:44Z
edit 2022-08-21T13:25:44Z
flannel 2022-08-22T17:06:43Z
kubeadm:get-nodes 2022-08-21T13:25:46Z
system:aggregate-to-admin 2022-08-21T13:25:44Z
system:aggregate-to-edit 2022-08-21T13:25:45Z
system:aggregate-to-view 2022-08-21T13:25:45Z
system:auth-delegator 2022-08-21T13:25:45Z
system:basic-user 2022-08-21T13:25:44Z
6.6 查看cluster-admin權限
[root@master opt]# kubectl describe clusterroles cluster-admin
Name: cluster-admin
Labels: kubernetes.io/bootstrapping=rbac-defaults
Annotations: rbac.authorization.kubernetes.io/autoupdate: true
PolicyRule:
Resources Non-Resource URLs Resource Names Verbs
--------- ----------------- -------------- -----
*.* [] [] [*]
[*] [] [*]
6.7 將服務賬戶 kubernetes-dashboard 跟 cluster-admin 這個集群管理員權限物件系結
[root@master opt]# cat > kubernetes-dashboard-ClusterRoleBinding.yaml << EOF
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: kubernetes-dashboard
labels:
k8s-app: kubernetes-dashboard
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: cluster-admin
subjects:
- kind: ServiceAccount
name: kubernetes-dashboard
namespace: kube-system
EOF
[root@master opt]# kubectl create -f kubernetes-dashboard-ClusterRoleBinding.yaml
6.8獲取登錄Token
[root@master opt]# kubectl -n kube-system describe secret $(kubectl -n kube-system get secret | grep admin | awk '{print $1}')
Name: admin-token-t4sxg
Namespace: kube-system
Labels: <none>
Annotations: kubernetes.io/service-account.name: admin
kubernetes.io/service-account.uid: 9f6ec4cf-925f-4d9f-a104-8e7367d08c98
Type: kubernetes.io/service-account-token
Data
=https://www.cnblogs.com/ewindstorm/archive/2022/08/23/===
ca.crt: 1066 bytes
namespace: 11 bytes
token: eyJhbGciOiJSUzI1NiIsImtpZCI6ImdyX0lGZm9xNlNrbTRxQnJoeU1CREZPUFdTR0F0WmNxekEzZ29ITkRFY0EifQ.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJrdWJlLXN5c3RlbSIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VjcmV0Lm5hbWUiOiJhZG1pbi10b2tlbi10NHN4ZyIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VydmljZS1hY2NvdW50Lm5hbWUiOiJhZG1pbiIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VydmljZS1hY2NvdW50LnVpZCI6IjlmNmVjNGNmLTkyNWYtNGQ5Zi1hMTA0LThlNzM2N2QwOGM5OCIsInN1YiI6InN5c3RlbTpzZXJ2aWNlYWNjb3VudDprdWJlLXN5c3RlbTphZG1pbiJ9.mv7wGLXAFcThtrS5_zuIKG-MaYJkQ2pud72G5vNfUrQsqSXNn3Kqf0OjFhagvZ1By5fHbyahTGWSWtYOoZUSKNXk42kEbh1LnhkYyjLKtFI1hUvk5Fw4Scc1PgGUpIyE1KPd4V3_jH3U7P6Kz5GfjkGhcTNDenoqdXtJN7c8UeF6QaG9hYxLyKCEH2M7SJDHq8q8LBuLT12yfxrFl6tGq5U_LwyYmJNUdpTuFOuvBYJ-8hi_ptxpxRDvUJskuZBW4HIxNi5dnNsQUt7euhSWePqfsSYAfTdPmTH6UvpKTAv87i9CA3rVeb46Jek7TMC6so5QNWnqBFb5RXkFqja8PA
6.9訪問dashboard
特別注釋：由于這里使用了非443的埠 所以google和ie瀏覽器打不開dashboard界面，可使用火狐打開
連接地址：http://所分部的node節點的ip:30001 打開輸入以上token
6.10 解決無法用google瀏覽器無法打開的問題
[root@master opt]# mkdir kubernetes-dashboard-key && cd kubernetes-dashboard-key
# 生成證書請求的key
[root@master opt]#openssl genrsa -out dashboard.key 2048
# 生成csr
[root@master opt]#openssl req -new -out dashboard.csr -key dashboard.key -subj '/CN=192.168.56.202.113'
# 生成自簽證書
[root@master opt]# openssl x509 -req -in dashboard.csr -signkey dashboard.key -out dashboard.crt
# 洗掉原有證書
[root@master opt]# kubectl delete secret kubernetes-dashboard-certs -n kube-system
# 創建新證書的secret
[root@master opt]# kubectl create secret generic kubernetes-dashboard-certs --from-file=dashboard.key --from-file=dashboard.crt -n kube-system
[root@master opt]# kubectl get pod -n kube-system
洗掉pod，重啟
[root@master opt]# kubectl delete pod kubernetes-dashboard-7d6c598b5f-fvcg8 -n kube-system
6.11如果出現大量的404頁面
# 由于使用的創建dashboard的yaml檔案是 舊版本的檔案 要使用新的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.
apiVersion: v1
kind: Namespace
metadata:
name: kubernetes-dashboard
---
apiVersion: v1
kind: ServiceAccount
metadata:
labels:
k8s-app: kubernetes-dashboard
name: kubernetes-dashboard
namespace: kubernetes-dashboard
---
kind: Service
apiVersion: v1
metadata:
labels:
k8s-app: kubernetes-dashboard
name: kubernetes-dashboard
namespace: kubernetes-dashboard
spec:
ports:
- port: 443
targetPort: 8443
nodePort: 30000
selector:
k8s-app: kubernetes-dashboard
type: NodePort
---
apiVersion: v1
kind: Secret
metadata:
labels:
k8s-app: kubernetes-dashboard
name: kubernetes-dashboard-certs
namespace: kubernetes-dashboard
type: Opaque
---
apiVersion: v1
kind: Secret
metadata:
labels:
k8s-app: kubernetes-dashboard
name: kubernetes-dashboard-csrf
namespace: kubernetes-dashboard
type: Opaque
data:
csrf: ""
---
apiVersion: v1
kind: Secret
metadata:
labels:
k8s-app: kubernetes-dashboard
name: kubernetes-dashboard-key-holder
namespace: kubernetes-dashboard
type: Opaque
---
kind: ConfigMap
apiVersion: v1
metadata:
labels:
k8s-app: kubernetes-dashboard
name: kubernetes-dashboard-settings
namespace: kubernetes-dashboard
---
kind: Role
apiVersion: rbac.authorization.k8s.io/v1
metadata:
labels:
k8s-app: kubernetes-dashboard
name: kubernetes-dashboard
namespace: kubernetes-dashboard
rules:
# Allow Dashboard to get, update and delete Dashboard exclusive secrets.
- apiGroups: [""]
resources: ["secrets"]
resourceNames: ["kubernetes-dashboard-key-holder", "kubernetes-dashboard-certs", "kubernetes-dashboard-csrf"]
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.
- apiGroups: [""]
resources: ["services"]
resourceNames: ["heapster", "dashboard-metrics-scraper"]
verbs: ["proxy"]
- apiGroups: [""]
resources: ["services/proxy"]
resourceNames: ["heapster", "http:heapster:", "https:heapster:", "dashboard-metrics-scraper", "http:dashboard-metrics-scraper"]
verbs: ["get"]
---
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1
metadata:
labels:
k8s-app: kubernetes-dashboard
name: kubernetes-dashboard
rules:
# Allow Metrics Scraper to get metrics from the Metrics server
- apiGroups: ["metrics.k8s.io"]
resources: ["pods", "nodes"]
verbs: ["get", "list", "watch"]
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
labels:
k8s-app: kubernetes-dashboard
name: kubernetes-dashboard
namespace: kubernetes-dashboard
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: Role
name: kubernetes-dashboard
subjects:
- kind: ServiceAccount
name: kubernetes-dashboard
namespace: kubernetes-dashboard
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: kubernetes-dashboard
namespace: kubernetes-dashboard
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: kubernetes-dashboard
subjects:
- kind: ServiceAccount
name: kubernetes-dashboard
namespace: kubernetes-dashboard
---
kind: Deployment
apiVersion: apps/v1
metadata:
labels:
k8s-app: kubernetes-dashboard
name: kubernetes-dashboard
namespace: kubernetes-dashboard
spec:
replicas: 1
revisionHistoryLimit: 10
selector:
matchLabels:
k8s-app: kubernetes-dashboard
template:
metadata:
labels:
k8s-app: kubernetes-dashboard
spec:
containers:
- name: kubernetes-dashboard
image: kubernetesui/dashboard:v2.0.0-beta4
imagePullPolicy: Always
ports:
- containerPort: 8443
protocol: TCP
args:
- --auto-generate-certificates
- --namespace=kubernetes-dashboard
# 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
---
kind: Service
apiVersion: v1
metadata:
labels:
k8s-app: dashboard-metrics-scraper
name: dashboard-metrics-scraper
namespace: kubernetes-dashboard
spec:
ports:
- port: 8000
targetPort: 8000
selector:
k8s-app: dashboard-metrics-scraper
---
kind: Deployment
apiVersion: apps/v1
metadata:
labels:
k8s-app: dashboard-metrics-scraper
name: dashboard-metrics-scraper
namespace: kubernetes-dashboard
spec:
replicas: 1
revisionHistoryLimit: 10
selector:
matchLabels:
k8s-app: dashboard-metrics-scraper
template:
metadata:
labels:
k8s-app: dashboard-metrics-scraper
spec:
containers:
- name: dashboard-metrics-scraper
image: kubernetesui/metrics-scraper:v1.0.1
ports:
- containerPort: 8000
protocol: TCP
livenessProbe:
httpGet:
scheme: HTTP
path: /
port: 8000
initialDelaySeconds: 30
timeoutSeconds: 30
volumeMounts:
- mountPath: /tmp
name: tmp-volume
serviceAccountName: kubernetes-dashboard
# Comment the following tolerations if Dashboard must not be deployed on master
tolerations:
- key: node-role.kubernetes.io/master
effect: NoSchedule
volumes:
- name: tmp-volume
emptyDir: {}
重啟dashboard服務
[root@master opt]# kubectl delete -f kubernetes-dashboard.yaml
[root@master opt]# kubectl create -f kubernetes-dashboard.yaml
轉載請註明出處，本文鏈接：https://www.uj5u.com/qita/502582.html
標籤：其他
上一篇：十年老程式員：C、Python、Java 不可兼得，專心學好一門編程語言就行！
下一篇：網頁UI設計軟體：XD