k8s-master-2-集群搭完后管理操作-文档2-flannel和dashboard
1.等各个node都加入集群后,master上的管理操作(需要等到所有node节点都join加入集群再操作)
查看flannel在各个节点的部署,自动的,因为yaml文件是daemonset类型:
[root@master ~]# kubectl get pod -o wide -n kube-system |grep flannel
kube-flannel-ds-amd64-7hrwk 1/1 Running 0 6m57s 192.168.171.128 master <none> <none>
kube-flannel-ds-amd64-hvrgx 1/1 Running 0 6m57s 192.168.171.129 node1 <none> <none>
kube-flannel-ds-amd64-lsq72 1/1 Running 0 6m57s 192.168.171.130 node2 <none> <none>
[root@master ~]# kubectl get nodes #只要集群加入成功且flannel网络都成功,就为ready状态
NAME STATUS ROLES AGE VERSION
master Ready master 33m v1.14.2
node1 Ready <none> 28m v1.14.2
node2 Ready <none> 26m v1.14.2
[root@master ~]# kubectl get cs
NAME STATUS MESSAGE ERROR
scheduler Healthy ok
controller-manager Healthy ok
etcd-0 Healthy {"health":"true"}
[root@master ~]# kubectl create deployment nginx --image=nginx #创建一个nginx容器
deployment.apps/nginx created
[root@master ~]# kubectl get pod -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
nginx-65f88748fd-gt5nh 1/1 Running 0 5m7s 10.244.1.3 node1 <none> <none>
[root@master ~]# kubectl get deploy -o wide
NAME READY UP-TO-DATE AVAILABLE AGE CONTAINERS IMAGES SELECTOR
nginx 1/1 1 1 5m12s nginx nginx app=nginx
2.部署dashboard:
[root@master ~]# wget https://raw.githubusercontent.com/kubernetes/dashboard/v1.10.1/src/deploy/recommended/kubernetes-dashboard.yaml
[root@master ~]# rz
上传dashboard镜像和yaml文件
[root@master ~]# ls kubernetes-dashboard*
kubernetes-dashboard-amd64_v1.10.1.tar kubernetes-dashboard.yaml
[root@master ~]# docker load -i kubernetes-dashboard-amd64_v1.10.1.tar #导入dashboard镜像,其他节点也导入
[root@master ~]# docker images |grep dashboard
registry.cn-hangzhou.aliyuncs.com/google_containers/kubernetes-dashboard-amd64 v1.10.1 f9aed6605b81 11 months ago 122MB
k8s.gcr.io/kubernetes-dashboard-amd64 v1.10.0 0dab2435c100 15 months ago 122MB
[root@master ~]# cat 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: k8s.gcr.io/kubernetes-dashboard-amd64:v1.10.1
image: registry.cn-hangzhou.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
[root@master ~]# kubectl apply -f kubernetes-dashboard.yaml #部署dashboard
[root@master ~]# kubectl get pod -o wide -n kube-system |grep dashboard
kubernetes-dashboard-5d9599dc98-sx64x 1/1 Running 0 41s 10.244.2.2 node2 <none> <none>
[root@master ~]# kubectl get deploy -o wide -n kube-system |grep dashboard
kubernetes-dashboard 1/1 1 1 48s kubernetes-dashboard registry.cn-hangzhou.aliyuncs.com/google_containers/kubernetes-dashboard-amd64:v1.10.1 k8s-app=kubernetes-dashboard
[root@master ~]# kubectl get svc -o wide -n kube-system |grep dashboard
kubernetes-dashboard NodePort 10.1.133.19 <none> 443:30001/TCP 53s k8s-app=kubernetes-dashboard
创建dashbard的服务账号: dashboard-admin
[root@master ~]# kubectl create serviceaccount dashboard-admin -n kube-system #创建一个服务账号:dashboard-admin
下面进行服务账号和角色(集群角色带权限)的绑定: 绑定的名称也是:dashboard-admin (默认一个集群的角色:cluster-admin拥有集群所有权限)
[root@master ~]# kubectl create clusterrolebinding dashboard-admin --clusterrole=cluster-admin --serviceaccount=kube-system:dashboard-admin
查看dashbard的服务账号创建后自动创建的token值,做认证使用:
[root@master ~]# kubectl get secret -n kube-system |grep dashboard-admin-token #查看创建服务账号后自动创建的token名
dashboard-admin-token-rcjsd kubernetes.io/service-account-token 3 29s
[root@master ~]# kubectl describe secret dashboard-admin-token-rcjsd -n kube-system #查看详细的token值,可认证登录
Name: dashboard-admin-token-rcjsd
Namespace: kube-system
Labels: <none>
Annotations: kubernetes.io/service-account.name: dashboard-admin
kubernetes.io/service-account.uid: 0109caac-1984-11ea-b914-000c2947447c
Type: kubernetes.io/service-account-token
Data
====
ca.crt: 1025 bytes
namespace: 11 bytes
token: eyJhbGciOiJSUzI1NiIsImtpZCI6IiJ9.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJrdWJlLXN5c3RlbSIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VjcmV0Lm5hbWUiOiJkYXNoYm9hcmQtYWRtaW4tdG9rZW4tcmNqc2QiLCJrdWJlcm5ldGVzLmlvL3NlcnZpY2VhY2NvdW50L3NlcnZpY2UtYWNjb3VudC5uYW1lIjoiZGFzaGJvYXJkLWFkbWluIiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9zZXJ2aWNlLWFjY291bnQudWlkIjoiMDEwOWNhYWMtMTk4NC0xMWVhLWI5MTQtMDAwYzI5NDc0NDdjIiwic3ViIjoic3lzdGVtOnNlcnZpY2VhY2NvdW50Omt1YmUtc3lzdGVtOmRhc2hib2FyZC1hZG1pbiJ9.E3eh32AnClqaws7xodnrIEna-yLby3K4v_34EtU03yfQY6q-ASRHwXn4IL2ijMPeDL2aoBwIw9TCDKoMkljoXsufQkGDDwuwxmFM8-FsYWODhbQzecrqyoHN0z7rYfMYl6wA9_LsVhCpcPwAUFNTDa1fS0FuG48qCjNt1n08R0iJlRXIjR4mFdU9EnmYmkq4_ZvXr1R1KMVztsOrtYVAV23OWdBNZGQk7vvXk9-X_KZSZamYk0CmgEnAcU72u1zI7eKs_44caYW3CIQg7geyADN7irm8gN-p0_ODXIeSpa3tVFtNFGztUvJWogeC_2Pn2XrPUWYjVjwJoBFfCT-opw
注意:
1)k8s默认有个一个名为:cluster-admin的角色,这个角色拥有k8s集群的所有权限,
2)创建完服务账号后,默认会自动创建一个token,以secret方式保存,查看出来的token可用作认证登录
使用火狐浏览器访问登录:(其他浏览器不支持,需要做支持的设置或安装插件什么):https://node2的ip:30001 能跳转到登录页面,如下:
https://192.168.171.130:30001/
输入上面查出的token值,可登录dashboard界面,如下: