在21、22、200三台机器上安装Docker。安装命令：
在21、22、200三台主机上部署Docker。
~]# curl -fsSL https://get.docker.com | bash -s docker --mirror Aliyun/etc/docker/daemon.json
{ "graph": "/data/docker", "storage-driver": "overlay2", "insecure-registries": ["registry.access.redhat.com","quay.io","harbor.od.com"], "registry-mirrors": ["https://q2gr04ke.mirror.aliyuncs.com"], "bip": "172.7.21.1/24", "exec-opts": ["native.cgroupdriver=systemd"], "live-restore": true}说明：
exec-opts：CPU/MEM的资源管理方式
registry-mirrors：镜像源
insecure-registries：信任的HTTP镜像仓库
bip根据不同的主机修改：
21:172.7.21.1/24
22:172.7.22.1/24
200: 172.7.200.1/24
创建目录
[root@hdss7-21 ~]# mkdir -pv /data/dockermkdir: created directory ‘/data’mkdir: created directory ‘/data/docker’[root@hdss7-21 ~]#~]# systemctl enable docker~]# systemctl start docker~]# systemctl status docker -l~]# docker info~]# docker version| 主机名 | 角色 | IP |
|---|---|---|
| CFZX55-21.host.com | kube-apiserver | 10.211.55.21 |
| CFZX55-22.host.com | kube-apiserver | 10.211.55.22 |
| CFZX55-11.host.com | 4层负载均衡 Nginx+Keepalived | 10.211.55.11 |
| CFZX55-12.host.com | 4层负载均衡 Nginx+Keepalived | 10.211.55.12 |
注意：这里10.211.55.11和10.211.55.12使用nginx做4层负载均衡，用keepalived跑一个vip：10.211.55.10，代理两个kube-apiserver，实现高可用。
在21主机上操作
本例使用1.23.4版本。
[root@cfzx55-21 src]# tar xf kubernetes-server-linux-amd64.tar.gz -C /opt/[root@cfzx55-21 src]# cd ..[root@cfzx55-21 kubernetes]# rm kubernetes-src.tar.gz -f[root@cfzx55-21 kubernetes]# rm -rf LICENSES/[root@cfzx55-21 kubernetes]# rm -rf addons/[root@cfzx55-21 kubernetes]# cd server/[root@cfzx55-21 server]# mv bin/ ../[root@cfzx55-21 server]# cd ..[root@cfzx55-21 kubernetes]# rm -rf server/[root@cfzx55-21 kubernetes]# cd bin/[root@cfzx55-21 bin]# rm *.tar -f[root@cfzx55-21 bin]# rm *_tag -f[root@cfzx55-21 opt]# vim /etc/profileexport PATH=$PATH:/opt/etcd:/opt/kubernetes/bin[root@cfzx55-21 opt]# source /etc/profile在200主机上操作
/opt/certs/kube-apiserver-csr.json
{ "CN": "kube-apiserver", "hosts": [ "127.0.0.1", "192.168.0.1", "kubernetes", "kubernetes.default", "kubernetes.default.svc", "kubernetes.default.svc.cluster", "kubernetes.default.svc.cluster.local", "10.211.55.10", "10.211.55.21", "10.211.55.22", "10.211.55.23" ], "key": { "algo": "rsa", "size": 2048 }, "names": [ { "C": "CN", "ST": "beijing", "L": "beijing", "O": "system:masters", "OU": "system" } ]}说明：
- CN：K8S会提取CN字段的值作为用户名，实际是指K8S的"RoleBinding/ClusterRoleBinding"资源中，“subjects.kind”的值为“User"，
- hosts：包括所有Master节点的IP地址，LB节点、LB集群节点、ClusterIP的首个IP，K8S的“ClusterIP”的范围在“--service-cluster-ip-range”中指定，取值为192.168.0.0/16，此处配置为192.168.0.1
- names
- C：CN
- ST：
- L：
- O：“system:masters”，定义“O”值的原因：apiserver向kubelet发起请求时，将复用此证书，参看官方文档。K8S默认会提取“O”字段的值作为组，这实际是指K8S的“RoleBinding/ClusterRoleBinding”资源中"subjects.kind"的值为“Group”，
生成证书
[root@cfzx55-200 certs]# cfssl gencert \> -ca=ca.pem \> -ca-key=ca-key.pem \> -config=ca-config.json \> -profile=kubernetes \> kube-apiserver-csr.json | cfssl-json -bare kube-apiserver2022/03/12 21:28:43 [INFO] generate received request2022/03/12 21:28:43 [INFO] received CSR2022/03/12 21:28:43 [INFO] generating key: rsa-20482022/03/12 21:28:43 [INFO] encoded CSR2022/03/12 21:28:43 [INFO] signed certificate with serial number 218531774642654852589087643914770351081106577228[root@cfzx55-200 certs]# ll kube-apiserver*-rw-r--r-- 1 root root 636 Mar 12 21:27 kube-apiserver-csr.json-rw------- 1 root root 1679 Mar 12 21:28 kube-apiserver-key.pem-rw-r--r-- 1 root root 1289 Mar 12 21:28 kube-apiserver.csr-rw-r--r-- 1 root root 1655 Mar 12 21:28 kube-apiserver.pem[root@cfzx55-200 certs]#在21主机上操作，把6张证书和密钥从200主机上拷贝到certs目录下
[root@cfzx55-21 certs]# pwd/opt/kubernetes/certs[root@cfzx55-21 certs]# lltotal 24-rw------- 1 root root 1679 Mar 12 21:32 ca-key.pem-rw-r--r-- 1 root root 1310 Mar 12 21:32 ca.pem-rw------- 1 root root 1675 Mar 12 21:32 etcd-key.pem-rw-r--r-- 1 root root 1448 Mar 12 21:32 etcd.pem-rw------- 1 root root 1679 Mar 12 21:32 kube-apiserver-key.pem-rw-r--r-- 1 root root 1655 Mar 12 21:32 kube-apiserver.pem[root@cfzx55-21 certs]#该文件的作用是，在工作节点（kubelet）加入K8S集群的过程中，向kube-apiserver申请签发证书。
/opt/kubernetes/bin/certs/kube-apiserver.token.csv
[root@cfzx55-21 certs]# head -c 16 /dev/urandom | od -An -t x | tr -d " "cceb7b589306a60ab6afe922f1f32d50[root@cfzx55-21 certs]# echo cceb7b589306a60ab6afe922f1f32d50,kubelet-bootstrap,10001,"system:kubelet-bootstrap" > kube-apiserver.token.csv[root@cfzx55-21 certs]# cat kube-apiserver.token.csvcceb7b589306a60ab6afe922f1f32d50,kubelet-bootstrap,10001,system:kubelet-bootstrap[root@cfzx55-21 certs]#在21主机上操作
创建启动脚本
/opt/kubernetes/bin/kube-apiserver-startup.sh
#!/bin/bash./kube-apiserver \ --runtime-config=api/all=true \ --anonymous-auth=false \ --bind-address=0.0.0.0 \ --advertise-address=10.211.55.21 \ --secure-port=6443 \ --tls-cert-file=./certs/kube-apiserver.pem \ --tls-private-key-file=./certs/kube-apiserver-key.pem \ --client-ca-file=./certs/ca.pem \ --etcd-cafile=./certs/ca.pem \ --etcd-certfile=./certs/etcd.pem \ --etcd-keyfile=./certs/etcd-key.pem \ --etcd-servers=https://10.211.55.12:2379,https://10.211.55.21:2379,https://10.211.55.22:2379 \ --kubelet-client-certificate=./certs/kube-apiserver.pem \ --kubelet-client-key=./certs/kube-apiserver-key.pem \ --service-account-key-file=./certs/ca.pem \ --service-account-signing-key-file=./certs/ca-key.pem \ --service-account-issuer=https://kubernetes.default.svc.cluster.local \ --enable-bootstrap-token-auth=true \ --token-auth-file=./certs/kube-apiserver.token.csv \ --allow-privileged=true \ --service-cluster-ip-range=192.168.0.0/16 \ --service-node-port-range=8000-20000 \ --authorization-mode=RBAC,Node \ --enable-aggregator-routing=true \ --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,ResourceQuota,NodeRestriction \ --v=2 \ --audit-log-path=/data/logs/kubernetes/kube-apiserver/audit-log \ --log-dir=/data/logs/kubernetes/kube-apiserver[root@cfzx55-21 bin]# chmod +x kube-apiserver-startup.sh[root@cfzx55-21 bin]# mkdir -pv /data/logs/kubernetes/kube-apiserver/etc/supervisord.d/kube-apiserver.ini
[program:kube-apiserver-55-21]command=/opt/kubernetes/bin/kube-apiserver-startup.shnumprocs=1directory=/opt/kubernetes/binautostart=trueautorestart=truestartsecs=30startretries=3exitcodes=0,2stopsignal=QUITstopwaitsecs=10user=rootredirect_stderr=truestdout_logfile=/data/logs/kubernetes/kube-apiserver/apiserver.stdout.logstdout_logfile_maxbytes=64MBstdout_logfile_backups=5stdout_capture_maxbytes=1MBstdout_events_enabled=false[root@cfzx55-21 bin]# supervisorctl update[root@cfzx55-21 bin]# supervisorctl statusetcd-server-55-21 RUNNING pid 12536, uptime 2:29:07kube-apiserver-55-21 RUNNING pid 13122, uptime 0:00:40[root@cfzx55-21 bin]# netstat -luntpActive Internet connections (only servers)Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program nametcp 0 0 0.0.0.0:6443 0.0.0.0:* LISTEN 13123/./kube-apisertcp 0 0 10.211.55.21:2379 0.0.0.0:* LISTEN 12537/./etcdtcp 0 0 127.0.0.1:2379 0.0.0.0:* LISTEN 12537/./etcdtcp 0 0 10.211.55.21:2380 0.0.0.0:* LISTEN 12537/./etcdtcp 0 0 10.211.55.21:2381 0.0.0.0:* LISTEN 12537/./etcdtcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 912/sshdudp 0 0 127.0.0.1:323 0.0.0.0:* 700/chronyd[root@cfzx55-21 bin]#安装22节点
# 在21节点上，把kubernetes文件拷贝到22节点[root@cfzx55-21 ~]# scp -r /opt/kubernetes/ root@cfzx55-22:/opt/[root@cfzx55-21 ~]# scp /etc/supervisord.d/kube-apiserver.ini root@cfzx55-22:/etc/supervisord.d/# 在22节点上，创建目录[root@cfzx55-22 certs]# mkdir -pv /data/logs/kubernetes/kube-apiserver# 修改 kube-apiserver-startup.sh 中的ip地址# 修改 /etc/supervisord.d/kube-apiserver.ini 中的名称# 启动[root@cfzx55-22 bin]# supervisorctl update[root@cfzx55-22 bin]# supervisorctl statusetcd-server-55-22 RUNNING pid 12495, uptime 2:37:27kube-apiserver-55-22 RUNNING pid 12675, uptime 0:00:38[root@cfzx55-22 bin]# netstat -luntpActive Internet connections (only servers)Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program nametcp 0 0 0.0.0.0:6443 0.0.0.0:* LISTEN 12676/./kube-apisertcp 0 0 10.211.55.22:2379 0.0.0.0:* LISTEN 12496/./etcdtcp 0 0 127.0.0.1:2379 0.0.0.0:* LISTEN 12496/./etcdtcp 0 0 10.211.55.22:2380 0.0.0.0:* LISTEN 12496/./etcdtcp 0 0 10.211.55.22:2381 0.0.0.0:* LISTEN 12496/./etcdtcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 914/sshdudp 0 0 127.0.0.1:323 0.0.0.0:* 704/chronyd[root@cfzx55-22 bin]#检查集群状态
[root@cfzx55-21 ~]# curl --insecure https://10.211.55.21:6443/{ "kind": "Status", "apiVersion": "v1", "metadata": {}, "status": "Failure", "message": "Unauthorized", "reason": "Unauthorized", "code": 401}[root@cfzx55-21 ~]# curl --insecure https://10.211.55.22:6443/{ "kind": "Status", "apiVersion": "v1", "metadata": {}, "status": "Failure", "message": "Unauthorized", "reason": "Unauthorized", "code": 401}[root@cfzx55-21 ~]#至此，kube-apiserver安装完成。
apiserver监听端口
[root@cfzx55-21 ~]# netstat -luntp | grep kubetcp 0 0 0.0.0.0:6443 0.0.0.0:* LISTEN 13123/./kube-apiser[root@cfzx55-22 ~]# netstat -luntp | grep kubetcp 0 0 0.0.0.0:6443 0.0.0.0:* LISTEN 12676/./kube-apiser用keepalived跑一个10.211.55.10的vip
用10.211.55.10上的7443，反向代理10.211.55.21和10.211.55.22上的6443端口。
下面的操作在11和12主机上进行。
安装nginx
~]# yum install nginx -y~]# yum install nginx-mod-stream -y配置nginx
把下面内容，添加到/etc/nginx/nginx.conf文件最后，也就是并列在http模块的后面。
stream { upstream kube-apiserver { server 10.211.55.21:6443 max_fails=3 fail_timeout=30s; server 10.211.55.22:6443 max_fails=3 fail_timeout=30s; } server { listen 7443; proxy_connect_timeout 2s; proxy_timeout 900s; proxy_pass kube-apiserver; }}[root@cfzx55-11 ~]# nginx -tnginx: [emerg] unknown directive "stream" in /etc/nginx/nginx.conf:85nginx: configuration file /etc/nginx/nginx.conf test failed上面错误提示，是因为没有安装stream模块。
启动nginx
~]# systemctl start nginx~]# systemctl enable nginx~]# systemctl status nginx检查状态
[root@cfzx55-11 ~]# netstat -luntp | grep nginxtcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 1499/nginx: mastertcp 0 0 0.0.0.0:7443 0.0.0.0:* LISTEN 1499/nginx: master[root@cfzx55-11 ~]#安装keepalived
[root@cfzx55-11 ~]# yum install keepalived -y[root@hdss7-12 ~]# yum install keepalived -y创建监听脚本
/etc/keepalived/check_port.sh
#!/bin/bashCHK_PORT=$1if [ -n "$CHK_PORT" ];then PORT_PROCESS=`ss -lnt | grep $CHK_PORT | wc -l` if [ $PORT_PROCESS -eq 0 ];then echo "Port $CHK_PORT Is Not Used, End." exit 1 fielse echo "Check Port Cant Be Empty!"fi增加执行权限
~]# chmod +x /etc/keepalived/check_port.sh测试脚本
[root@cfzx55-11 ~]# /etc/keepalived/check_port.shCheck Port Cant Be Empty![root@cfzx55-11 ~]# /etc/keepalived/check_port.sh 7443[root@cfzx55-11 ~]# echo $?0[root@cfzx55-11 ~]# /etc/keepalived/check_port.sh 7445Port 7445 Is Not Used, End.[root@cfzx55-11 ~]# echo $?1[root@cfzx55-11 ~]#keepalived主配置
在11主机上操作
/etc/keepalived/keepalived.conf
! Configuration File for keepalivedglobal_defs { router_id 10.211.55.11}vrrp_script chk_nginx { script "/etc/keepalived/check_port.sh 7443" interval 2 weight -20}vrrp_instance VI_1 { state MASTER interface eth0 virtual_router_id 251 priority 100 advert_int 1 mcast_src_ip 10.211.55.11 nopreempt #设置非抢占式，当主服务down，vip漂移到备机，当主机服务up，vip依然在备机上 authentication { auth_type PASS auth_pass 11111111 } track_script { chk_nginx } virtual_ipaddress { 10.211.55.10 }}keepalived从配置
在12主机上操作
/etc/keepalived/keepalived.conf
! Configuration File for keepalived global_defs { router_id 10.211.55.12} vrrp_script chk_nginx { script "/etc/keepalived/check_port.sh 7443" interval 2 weight -20} vrrp_instance VI_1 { state BACKUP interface eth0 virtual_router_id 251 priority 90 advert_int 1 mcast_src_ip 10.211.55.12 ! 注意 备机上不能有 nopreempt 配置 authentication { auth_type PASS auth_pass 11111111 } track_script { chk_nginx } virtual_ipaddress { 10.211.55.10 }}在11主机上操作
[root@cfzx55-11 ~]# systemctl enable keepalivedCreated symlink from /etc/systemd/system/multi-user.target.wants/keepalived.service to /usr/lib/systemd/system/keepalived.service.[root@cfzx55-11 ~]# systemctl start keepalived[root@cfzx55-11 ~]# systemctl status keepalived● keepalived.service - LVS and VRRP High Availability Monitor Loaded: loaded (/usr/lib/systemd/system/keepalived.service; enabled; vendor preset: disabled) Active: active (running) since Sun 2022-03-13 08:21:53 CST; 6s ago Process: 1580 ExecStart=/usr/sbin/keepalived $KEEPALIVED_OPTIONS (code=exited, status=0/SUCCESS) Main PID: 1581 (keepalived) CGroup: /system.slice/keepalived.service ├─1581 /usr/sbin/keepalived -D ├─1582 /usr/sbin/keepalived -D └─1583 /usr/sbin/keepalived -DMar 13 08:21:53 cfzx55-11.host.com Keepalived_healthcheckers[1582]: Opening file '/etc/keepalive....Mar 13 08:21:54 cfzx55-11.host.com Keepalived_vrrp[1583]: VRRP_Instance(VI_1) Transition to MAS...TEMar 13 08:21:55 cfzx55-11.host.com Keepalived_vrrp[1583]: VRRP_Instance(VI_1) Entering MASTER STATEMar 13 08:21:55 cfzx55-11.host.com Keepalived_vrrp[1583]: VRRP_Instance(VI_1) setting protocol VIPs.Mar 13 08:21:55 cfzx55-11.host.com Keepalived_vrrp[1583]: Sending gratuitous ARP on eth0 for 10...10Mar 13 08:21:55 cfzx55-11.host.com Keepalived_vrrp[1583]: VRRP_Instance(VI_1) Sending/queueing ...10Mar 13 08:21:55 cfzx55-11.host.com Keepalived_vrrp[1583]: Sending gratuitous ARP on eth0 for 10...10Mar 13 08:21:55 cfzx55-11.host.com Keepalived_vrrp[1583]: Sending gratuitous ARP on eth0 for 10...10Mar 13 08:21:55 cfzx55-11.host.com Keepalived_vrrp[1583]: Sending gratuitous ARP on eth0 for 10...10Mar 13 08:21:55 cfzx55-11.host.com Keepalived_vrrp[1583]: Sending gratuitous ARP on eth0 for 10...10Hint: Some lines were ellipsized, use -l to show in full.[root@cfzx55-11 ~]#在12主机上操作
[root@cfzx55-12 ~]# systemctl enable keepalivedCreated symlink from /etc/systemd/system/multi-user.target.wants/keepalived.service to /usr/lib/systemd/system/keepalived.service.[root@cfzx55-12 ~]# systemctl start keepalived[root@cfzx55-12 ~]# systemctl status keepalived● keepalived.service - LVS and VRRP High Availability Monitor Loaded: loaded (/usr/lib/systemd/system/keepalived.service; enabled; vendor preset: disabled) Active: active (running) since Sun 2022-03-13 08:22:29 CST; 7s ago Process: 1538 ExecStart=/usr/sbin/keepalived $KEEPALIVED_OPTIONS (code=exited, status=0/SUCCESS) Main PID: 1539 (keepalived) CGroup: /system.slice/keepalived.service ├─1539 /usr/sbin/keepalived -D ├─1540 /usr/sbin/keepalived -D └─1541 /usr/sbin/keepalived -DMar 13 08:22:29 cfzx55-12.host.com Keepalived_vrrp[1541]: Registering gratuitous ARP shared channelMar 13 08:22:29 cfzx55-12.host.com Keepalived_vrrp[1541]: Opening file '/etc/keepalived/keepali...'.Mar 13 08:22:29 cfzx55-12.host.com Keepalived_vrrp[1541]: WARNING - default user 'keepalived_sc...e.Mar 13 08:22:29 cfzx55-12.host.com Keepalived_vrrp[1541]: Unable to access script `/etc/keepali...h`Mar 13 08:22:29 cfzx55-12.host.com Keepalived_vrrp[1541]: Disabling track script chk_nginx sinc...ndMar 13 08:22:29 cfzx55-12.host.com Keepalived_vrrp[1541]: VRRP_Instance(VI_1) removing protocol...s.Mar 13 08:22:29 cfzx55-12.host.com Keepalived_vrrp[1541]: Using LinkWatch kernel netlink reflec.....Mar 13 08:22:29 cfzx55-12.host.com Keepalived_vrrp[1541]: VRRP_Instance(VI_1) Entering BACKUP STATEMar 13 08:22:29 cfzx55-12.host.com Keepalived_vrrp[1541]: VRRP sockpool: [ifindex(2), proto(112...)]Mar 13 08:22:29 cfzx55-12.host.com Keepalived_healthcheckers[1540]: Opening file '/etc/keepalive....Hint: Some lines were ellipsized, use -l to show in full.[root@cfzx55-12 ~]#在11上用ip addr命令，能看到VIP
[root@cfzx55-11 ~]# ip addr1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc link/ether 00:1c:42:76:65:e1 brd ff:ff:ff:ff:ff:ff inet 10.211.55.11/24 brd 10.211.55.255 scope global noprefixroute eth0 valid_lft forever preferred_lft forever inet 10.211.55.10/32 scope global eth0 valid_lft forever preferred_lft forever[root@cfzx55-11 ~]#Nginx+Keepalived高可用测试
在11主机上，停止nginx，vip不存在了。
[root@cfzx55-11 ~]# systemctl stop nginx[root@cfzx55-11 ~]# ip a1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc link/ether 00:1c:42:76:65:e1 brd ff:ff:ff:ff:ff:ff inet 10.211.55.11/24 brd 10.211.55.255 scope global noprefixroute eth0 valid_lft forever preferred_lft forever[root@cfzx55-11 ~]#12主机上查看，vip跑在了12主机上
[root@cfzx55-12 ~]# ip a1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc link/ether 00:1c:42:e2:45:7b brd ff:ff:ff:ff:ff:ff inet 10.211.55.12/24 brd 10.211.55.255 scope global noprefixroute eth0 valid_lft forever preferred_lft forever inet 10.211.55.10/32 scope global eth0 valid_lft forever preferred_lft forever[root@cfzx55-12 ~]#重启nginx，vip还在12主机上。
这是因为在11上配置了 nopreempt ，设置非抢占式，当主服务down，vip漂移到备机，当主机服务up，vip依然在备机上。
如果要想vip回到11上，重新启动keepalived。
| 主机名 | 角色 | IP |
|---|---|---|
| CFZX55-21.host.com | kubectl | 10.211.55.21 |
| CFZX55-22.host.com | kubectl | 10.211.55.22 |
在运维主机200上操作
生成kubectl证书请求csr文件
/opt/certs/kubectl-csr.json
{ "CN": "clusteradmin", "hosts": [], "key": { "algo": "rsa", "size": 2048 }, "names": [ { "C": "CN", "ST": "beijing", "L": "beijing", "O": "system:masters", "OU": "system" } ]}说明
- CN：kubectl证书中的CN值没有意义，随便取值
- O：因为希望使用kubectl时有完整的集群操作权限，所以取值为“system:masters”，K8S默认会提取O字段的值作为组，这实际是指K8S里“RoleBinding/ClusterRoleBinding”资源中"subjects.kind"的值为“Group”
- 后续 kube-apiserver 使用 RBAC 对客户端(如 kubelet、kube-proxy、Pod)请求进行授权；
kube-apiserver 预定义了一些 RBAC 使用的 RoleBindings，如 cluster-admin 将 Group system:masters 与 Role cluster-admin 绑定，该 Role 授予了调用kube-apiserver 的所有 API的权限；- O指定该证书的 Group 为 system:masters，kubelet 使用该证书访问 kube-apiserver 时 ，由于证书被 CA 签名，所以认证通过，同时由于证书用户组为经过预授权的 system:masters，所以被授予访问所有 API 的权限；
- 这个证书，是将来生成管理员用的kube config 配置文件用的，现在我们一般建议使用RBAC 来对kubernetes 进行角色权限控制， kubernetes 将证书中的CN 字段 作为User， O 字段作为 Group；
"O": "system:masters", 必须是system:masters，否则后面kubectl create clusterrolebinding报错。
生成证书
[root@cfzx55-200 certs]# cfssl gencert \> -ca=ca.pem \> -ca-key=ca-key.pem \> -config=ca-config.json \> -profile=kubernetes \> kubectl-csr.json | cfssl-json -bare kubectl2022/03/13 08:48:36 [INFO] generate received request2022/03/13 08:48:36 [INFO] received CSR2022/03/13 08:48:36 [INFO] generating key: rsa-20482022/03/13 08:48:36 [INFO] encoded CSR2022/03/13 08:48:36 [INFO] signed certificate with serial number 6299036701939125919064904784479302515578648687552022/03/13 08:48:36 [WARNING] This certificate lacks a "hosts" field. This makes it unsuitable forwebsites. For more information see the Baseline Requirements for the Issuance and Managementof Publicly-Trusted Certificates, v.1.1.6, from the CA/Browser Forum (https://cabforum.org);specifically, section 10.2.3 ("Information Requirements").[root@cfzx55-200 certs]# ll kubectl*-rw-r--r-- 1 root root 1017 Mar 13 08:48 kubectl.csr-rw-r--r-- 1 root root 306 Mar 13 08:44 kubectl-csr.json-rw------- 1 root root 1679 Mar 13 08:48 kubectl-key.pem-rw-r--r-- 1 root root 1411 Mar 13 08:48 kubectl.pem[root@cfzx55-200 certs]#[root@cfzx55-200 certs]# scp kubectl*.pem root@cfzx55-21:/opt/kubernetes/bin/certs/[root@cfzx55-200 certs]# scp kubectl*.pem root@cfzx55-22:/opt/kubernetes/bin/certs/生成kubectl组件的kubectl.kubeconfig配置文件，该文件包含访问kube-apiseerver的所有信息，如kube-apiserver的地址，CA证书和自身使用的证书。
有了这个文件，便可以在任何机器上以超级管理员身份对K8S集群做任何操作，请务必保证此文件的安全性。
kubectl命令默认使用的配置文件为：~/.kube.config
以下在21主机上操作，完成后把生成的文件拷贝到其余Master节点，本例是22主机。
生成创建配置文件的脚本
#!/bin/bashKUBE_CONFIG="/root/.kube/config"KUBE_APISERVER="https://10.211.55.10:7443"kubectl config set-cluster kubernetes \ --certificate-authority=/opt/kubernetes/bin/certs/ca.pem \ --embed-certs=true \ --server=${KUBE_APISERVER} \ --kubeconfig=${KUBE_CONFIG} kubectl config set-credentials clusteradmin \ --client-certificate=/opt/kubernetes/bin/certs/kubectl.pem \ --client-key=/opt/kubernetes/bin/certs/kubectl-key.pem \ --embed-certs=true \ --kubeconfig=${KUBE_CONFIG} kubectl config set-context default \ --cluster=kubernetes \ --user=clusteradmin \ --kubeconfig=${KUBE_CONFIG} kubectl config use-context default --kubeconfig=${KUBE_CONFIG}说明：
- 集群名称：描述集群信息的标记，没有实际意义。
- certificate-authority：K8S集群的根CA证书
- server：指向kube-apiserrver负载均衡器VIP的地址
- kubeconfig：生成的kubeconfig文件
- 用户名称：clusteradmin为定义一个用户，在kubeconfig配置文件中，这个用户用于关联一组证书，这个证书对K8S集群来说无实际意义，真正重要的是证书中的O字段与CN字段的定义。
- client-certificate：客户端证书
- client-key：客户端私钥
- 上下文：default用于将kubeconfig配置文件“clusteradmin”和“kubernetes”作关联。
- cluster：set-cluster命令配置的集群名称。
- cluster：set-credentials命令配置的用户名称。
执行脚本
[root@cfzx55-21 ~]# mkdir ~/.kube[root@cfzx55-21 ~]# mkdir k8s-shell[root@cfzx55-21 ~]# cd k8s-shell/[root@cfzx55-21 k8s-shell]# vim kubectl-config.sh[root@cfzx55-21 k8s-shell]# chmod +x kubectl-config.sh[root@cfzx55-21 k8s-shell]# ./kubectl-config.shCluster "kubernetes" set.User "clusteradmin" set.Context "default" created.Switched to context "default".[root@cfzx55-21 k8s-shell]#查看集群状态
[root@cfzx55-21 k8s-shell]# kubectl cluster-infoKubernetes control plane is running at https://10.211.55.10:7443To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.[root@cfzx55-21 k8s-shell]# kubectl get componentstatusesWarning: v1 ComponentStatus is deprecated in v1.19+NAME STATUS MESSAGE ERRORcontroller-manager Unhealthy Get "https://127.0.0.1:10257/healthz": dial tcp 127.0.0.1:10257: connect: connection refusedscheduler Unhealthy Get "https://127.0.0.1:10259/healthz": dial tcp 127.0.0.1:10259: connect: connection refusedetcd-1 Healthy {"health":"true","reason":""}etcd-2 Healthy {"health":"true","reason":""}etcd-0 Healthy {"health":"true","reason":""}[root@cfzx55-21 k8s-shell]# kubectl get all -ANAMESPACE NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGEdefault service/kubernetes ClusterIP 192.168.0.1 <none> 443/TCP 10h[root@cfzx55-21 k8s-shell]#把21主机上生成的kubeconfig文件拷贝到22节点
[root@cfzx55-22 ~]# mkdir ~/.kube[root@cfzx55-22 ~]# scp root@cfzx55-21:/root/.kube/config ~/.kube/[root@cfzx55-22 ~]# ll .kube/total 8-rw------- 1 root root 6224 Mar 13 09:42 config[root@cfzx55-22 ~]#在22上查看集群状态
[root@cfzx55-22 ~]# kubectl cluster-infoKubernetes control plane is running at https://10.211.55.10:7443To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.[root@cfzx55-22 ~]# kubectl get componentstatusesWarning: v1 ComponentStatus is deprecated in v1.19+NAME STATUS MESSAGE ERRORcontroller-manager Unhealthy Get "https://127.0.0.1:10257/healthz": dial tcp 127.0.0.1:10257: connect: connection refusedscheduler Unhealthy Get "https://127.0.0.1:10259/healthz": dial tcp 127.0.0.1:10259: connect: connection refusedetcd-2 Healthy {"health":"true","reason":""}etcd-1 Healthy {"health":"true","reason":""}etcd-0 Healthy {"health":"true","reason":""}[root@cfzx55-22 ~]# kubectl get all -ANAMESPACE NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGEdefault service/kubernetes ClusterIP 192.168.0.1 <none> 443/TCP 11h[root@cfzx55-22 ~]#至此，kubectl主机部署完成。
| 主机名 | 角色 | IP |
|---|---|---|
| CFZX55-21.host.com | controller-manager | 10.211.55.21 |
| CFZX55-22.host.com | controller-manager | 10.211.55.22 |
在运维主机200上操作。
生成证书请求文件
/opt/certs/kube-controller-manager-csr.json
{ "CN": "system:kube-controller-manager", "hosts": [ "127.0.0.1", "10.211.55.11", "10.211.55.12", "10.211.55.21", "10.211.55.22", "10.211.55.23" ], "key": { "algo": "rsa", "size": 2048 }, "names": [ { "C": "CN", "ST": "beijing", "L": "beijing", "O": "system:masters", "OU": "system" } ]}说明：
- CN：这里的CN值非常重要，kube-controller-manager能否正常与kubee-apiserver通信与此值有关，K8S默认会提取CN字段的值作为用户名，这实际是指K8S的“RoleBinding/ClusterRoleBinding”资源中“subjects：kind”的值为“User”
- hosts：kube-controller-manager运行节点的IP地址。
- O：无实际意义。
- OU：无实际意义。
- hosts 列表包含所有 kube-controller-manager 节点 IP；
- CN 为 system:kube-controller-manager、O 为 system:kube-controller-manager，kubernetes 内置的 ClusterRoleBindings system:kube-controller-manager 赋予 kube-controller-manager 工作所需的权限
生成证书
[root@cfzx55-200 certs]# cfssl gencert \> -ca=ca.pem \> -ca-key=ca-key.pem \> -config=ca-config.json \> -profile=kubernetes \> kube-controller-manager-csr.json | cfssl-json -bare kube-controller-manager2022/03/13 10:35:55 [INFO] generate received request2022/03/13 10:35:55 [INFO] received CSR2022/03/13 10:35:55 [INFO] generating key: rsa-20482022/03/13 10:35:55 [INFO] encoded CSR2022/03/13 10:35:55 [INFO] signed certificate with serial number 386505557530275475753178134460007976778023939766[root@cfzx55-200 certs]# ll kube-controller*.pem-rw------- 1 root root 1679 Mar 13 10:35 kube-controller-manager-key.pem-rw-r--r-- 1 root root 1501 Mar 13 10:35 kube-controller-manager.pem[root@cfzx55-200 certs]#把证书拷贝到21和22主机上
[root@cfzx55-200 certs]# scp kube-controller-manager*.pem root@cfzx55-21:/opt/kubernetes/bin/certs/[root@cfzx55-200 certs]# scp kube-controller-manager*.pem root@cfzx55-22:/opt/kubernetes/bin/certs/配置文件路径：/opt/kubernetes/cfg/
编写生成kubeconfig配置文件的脚本
#!/bin/bashKUBE_CONFIG="/opt/kubernetes/cfg/kube-controller-manager.kubeconfig"KUBE_APISERVER="https://10.211.55.10:7443"kubectl config set-cluster kubernetes \ --certificate-authority=/opt/kubernetes/bin/certs/ca.pem \ --embed-certs=true \ --server=${KUBE_APISERVER} \ --kubeconfig=${KUBE_CONFIG} kubectl config set-credentials kube-controller-manager \ --client-certificate=/opt/kubernetes/bin/certs/kube-controller-manager.pem \ --client-key=/opt/kubernetes/bin/certs/kube-controller-manager-key.pem \ --embed-certs=true \ --kubeconfig=${KUBE_CONFIG} kubectl config set-context default \ --cluster=kubernetes \ --user=kube-controller-manager \ --kubeconfig=${KUBE_CONFIG} kubectl config use-context default --kubeconfig=${KUBE_CONFIG}生成配置文件
[root@cfzx55-21 k8s-shell]# vim kube-controller-manager-config.sh[root@cfzx55-21 k8s-shell]# chmod +x kube-controller-manager-config.sh[root@cfzx55-21 k8s-shell]# ./kube-controller-manager-config.shCluster "kubernetes" set.User "kube-controller-manager" set.Context "default" created.Switched to context "default".[root@cfzx55-21 k8s-shell]#把生成的配置文件拷贝到22主机上。
[root@cfzx55-21 ~]# scp -r /opt/kubernetes/cfg/ root@cfzx55-22:/opt/kubernetes/root@cfzx55-22's password:kube-controller-manager.kubeconfig 100% 6366 2.6MB/s 00:00[root@cfzx55-21 ~]#在22主机上查看
[root@cfzx55-22 ~]# ll /opt/kubernetes/cfg/total 8-rw------- 1 root root 6366 Mar 13 10:49 kube-controller-manager.kubeconfig[root@cfzx55-22 ~]#在21主机上操作
/opt/kubernetes/bin/kube-controller-manager-startup.sh
#!/bin/sh./kube-controller-manager \ --cluster-name=kubernetes \ --bind-address=127.0.0.1 \ --service-cluster-ip-range=192.168.0.0/16 \ --leader-elect=true \ --controllers=*,bootstrapsigner,tokencleaner \ --kubeconfig=/opt/kubernetes/cfg/kube-controller-manager.kubeconfig \ --tls-cert-file=./certs/kube-controller-manager.pem \ --tls-private-key-file=./certs/kube-controller-manager-key.pem \ --cluster-signing-cert-file=./certs/ca.pem \ --cluster-signing-key-file=./certs/ca-key.pem \ --cluster-signing-duration=175200h0m0s \ --use-service-account-credentials=true \ --root-ca-file=./certs/ca.pem \ --service-account-private-key-file=./certs/ca-key.pem \ --log-dir=/data/logs/kubernetes/kube-controller-manager \ --v=2说明：
--secure-port=10252 这个参数去掉，状态才能正常。--cluster-cidr string CIDR Range for Pods in cluster. Requires --allocate-node-cidrs to be true本例中，allocate-node-cidrs和cluster-cidr两个参数不配置，使用docker的bip。 创建脚本，调整权限
[root@cfzx55-21 bin]# vim kube-controller-manager-startup.sh[root@cfzx55-21 bin]# chmod +x kube-controller-manager-startup.sh[root@cfzx55-21 bin]#创建目录
[root@cfzx55-21 ~]# mkdir -p /data/logs/kubernetes/kube-controller-manager/etc/supervisord.d/kube-controller-manager.ini
[program:kube-controller-manager-55-21]command=/opt/kubernetes/bin/kube-controller-manager-startup.shnumprocs=1directory=/opt/kubernetes/binautostart=trueautorestart=truestartsecs=30startretries=3exitcodes=0,2stopsignal=QUITstopwaitsecs=10user=rootredirect_stderr=truestdout_logfile=/data/logs/kubernetes/kube-controller-manager/controller.stdout.logstdout_logfile_maxbytes=64MBstdout_logfile_backups=4stdout_capture_maxbytes=1MBstdout_events_enabled=false[root@cfzx55-21 bin]# supervisorctl start kube-controller-manager-55-21kube-controller-manager-55-21: started[root@cfzx55-21 bin]# supervisorctl statusetcd-server-55-21 RUNNING pid 1033, uptime 4:21:51kube-apiserver-55-21 RUNNING pid 1034, uptime 4:21:51kube-controller-manager-55-21 RUNNING pid 3330, uptime 0:00:37[root@cfzx55-21 bin]#[root@cfzx55-21 bin]# netstat -luntp | grep kubetcp 0 0 0.0.0.0:6443 0.0.0.0:* LISTEN 1044/./kube-apiservtcp 0 0 127.0.0.1:10252 0.0.0.0:* LISTEN 3331/./kube-control[root@cfzx55-21 bin]#[root@cfzx55-21 bin]# scp kube-controller-manager-startup.sh root@cfzx55-22:/opt/kubernetes/bin/root@cfzx55-22's password:kube-controller-manager-startup.sh 100% 778 489.1KB/s 00:00[root@cfzx55-21 bin]# scp /etc/supervisord.d/kube-controller-manager.ini root@cfzx55-22:/etc/supervisord.d/root@cfzx55-22's password:kube-controller-manager.ini 100% 474 326.8KB/s 00:00[root@cfzx55-21 bin]## 修改程序名称[root@cfzx55-22 ~]# vim /etc/supervisord.d/kube-controller-manager.ini[root@cfzx55-22 ~]# mkdir -p /data/logs/kubernetes/kube-controller-manager[root@cfzx55-22 ~]# supervisorctl updatekube-controller-manager-55-21: added process group[root@cfzx55-22 ~]# supervisorctl statusetcd-server-55-22 RUNNING pid 1013, uptime 4:27:39kube-apiserver-55-22 RUNNING pid 1012, uptime 4:27:39kube-controller-manager-55-21 RUNNING pid 3099, uptime 0:00:34[root@cfzx55-22 ~]# netstat -luntp | grep kubetcp 0 0 0.0.0.0:6443 0.0.0.0:* LISTEN 1014/./kube-apiservtcp 0 0 127.0.0.1:10252 0.0.0.0:* LISTEN 3100/./kube-control[root@cfzx55-22 ~]#| 主机名 | 角色 | IP |
|---|---|---|
| CFZX55-21.host.com | kube-scheduler | 10.211.55.21 |
| CFZX55-22.host.com | kube-scheduler | 10.211.55.22 |
创建证书请求csr文件
/opt/certs/kube-scheduler-csr.json
{ "CN": "system:kube-scheduler", "hosts": [ "127.0.0.1", "10.211.55.11", "10.211.55.12", "10.211.55.21", "10.211.55.22", "10.211.55.23" ], "key": { "algo": "rsa", "size": 2048 }, "names": [ { "C": "CN", "ST": "beijing", "L": "beijing", "O": "system:masters", "OU": "system" } ]}生成证书
[root@cfzx55-200 certs]# cfssl gencert \> -ca=ca.pem \> -ca-key=ca-key.pem \> -config=ca-config.json \> -profile=kubernetes \> kube-scheduler-csr.json | cfssl-json -bare kube-scheduler2022/03/13 12:30:21 [INFO] generate received request2022/03/13 12:30:21 [INFO] received CSR2022/03/13 12:30:21 [INFO] generating key: rsa-20482022/03/13 12:30:21 [INFO] encoded CSR2022/03/13 12:30:21 [INFO] signed certificate with serial number 78101929142938232987965103781662806513424359272[root@cfzx55-200 certs]# ll kube-scheduler*.pem-rw------- 1 root root 1679 Mar 13 12:30 kube-scheduler-key.pem-rw-r--r-- 1 root root 1489 Mar 13 12:30 kube-scheduler.pem[root@cfzx55-200 certs]#[root@cfzx55-200 certs]# scp kube-scheduler*.pem root@cfzx55-21:/opt/kubernetes/bin/certs/root@cfzx55-21's password:kube-scheduler-key.pem 100% 1679 957.6KB/s 00:00kube-scheduler.pem 100% 1489 953.3KB/s 00:00[root@cfzx55-200 certs]# scp kube-scheduler*.pem root@cfzx55-22:/opt/kubernetes/bin/certs/root@cfzx55-22's password:kube-scheduler-key.pem 100% 1679 640.6KB/s 00:00kube-scheduler.pem 100% 1489 794.6KB/s 00:00[root@cfzx55-200 certs]##!/bin/bashKUBE_CONFIG="/opt/kubernetes/cfg/kube-scheduler.kubeconfig"KUBE_APISERVER="https://10.211.55.10:7443"kubectl config set-cluster kubernetes \ --certificate-authority=/opt/kubernetes/bin/certs/ca.pem \ --embed-certs=true \ --server=${KUBE_APISERVER} \ --kubeconfig=${KUBE_CONFIG} kubectl config set-credentials kube-scheduler \ --client-certificate=/opt/kubernetes/bin/certs/kube-scheduler.pem \ --client-key=/opt/kubernetes/bin/certs/kube-scheduler-key.pem \ --embed-certs=true \ --kubeconfig=${KUBE_CONFIG} kubectl config set-context default \ --cluster=kubernetes \ --user=kube-scheduler \ --kubeconfig=${KUBE_CONFIG} kubectl config use-context default --kubeconfig=${KUBE_CONFIG}执行脚本
[root@cfzx55-21 k8s-shell]# vim kube-scheduler-config.sh[root@cfzx55-21 k8s-shell]# chmod +x kube-scheduler-config.sh[root@cfzx55-21 k8s-shell]# ./kube-scheduler-config.shCluster "kubernetes" set.User "kube-scheduler" set.Context "default" created.Switched to context "default".[root@cfzx55-21 k8s-shell]#把kubeconfig 文件拷贝到22主机
[root@cfzx55-21 k8s-shell]# scp /opt/kubernetes/cfg/kube-scheduler.kubeconfig root@cfzx55-22:/opt/kubernetes/cfg/root@cfzx55-22's password:kube-scheduler.kubeconfig 100% 6332 2.6MB/s 00:00[root@cfzx55-21 k8s-shell]#/opt/kubernetes/bin/kube-scheduler-startup.sh
#!/bin/sh./kube-scheduler \ --address=127.0.0.1 \ --leader-elect=true \ --kubeconfig=/opt/kubernetes/cfg/kube-scheduler.kubeconfig \ --log-dir=/data/logs/kubernetes/kube-scheduler \ --v=2创建脚本，调整权限
[root@cfzx55-21 bin]# vim kube-scheduler-startup.sh[root@cfzx55-21 bin]# chmod +x kube-scheduler-startup.sh[root@cfzx55-21 ~]# mkdir -p /data/logs/kubernetes/kube-scheduler/etc/supervisord.d/kube-scheduler.ini
[program:kube-scheduler-55-21]command=/opt/kubernetes/bin/kube-scheduler-startup.shnumprocs=1directory=/opt/kubernetes/binautostart=trueautorestart=truestartsecs=30startretries=3exitcodes=0,2stopsignal=QUITstopwaitsecs=10user=rootredirect_stderr=truestdout_logfile=/data/logs/kubernetes/kube-scheduler/scheduler.stdout.logstdout_logfile_maxbytes=64MBstdout_logfile_backups=4stdout_capture_maxbytes=1MBstdout_events_enabled=false[root@cfzx55-21 bin]# supervisorctl update[root@cfzx55-21 bin]# supervisorctl statusetcd-server-55-21 RUNNING pid 1033, uptime 5:16:26kube-apiserver-55-21 RUNNING pid 1034, uptime 5:16:26kube-controller-manager-55-21 RUNNING pid 3416, uptime 0:38:46kube-scheduler-55-21 RUNNING pid 3486, uptime 0:00:32[root@cfzx55-21 bin]# netstat -luntp | grep kubetcp 0 0 0.0.0.0:10259 0.0.0.0:* LISTEN 3487/./kube-schedultcp 0 0 0.0.0.0:6443 0.0.0.0:* LISTEN 1044/./kube-apiservtcp 0 0 127.0.0.1:10252 0.0.0.0:* LISTEN 3417/./kube-control[root@cfzx55-21 bin]#[root@cfzx55-21 bin]# scp kube-scheduler-startup.sh root@cfzx55-22:/opt/kubernetes/bin/root@cfzx55-22's password:kube-scheduler-startup.sh 100% 199 100.3KB/s 00:00[root@cfzx55-21 bin]#[root@cfzx55-21 bin]# scp /etc/supervisord.d/kube-scheduler.ini root@cfzx55-22:/etc/supervisord.d/root@cfzx55-22's password:kube-scheduler.ini 100% 446 329.4KB/s 00:00[root@cfzx55-21 bin]## 修改名称[root@cfzx55-22 ~]# vim /etc/supervisord.d/kube-scheduler.ini[root@cfzx55-22 ~]# supervisorctl updatekube-controller-manager-55-21: stoppedkube-controller-manager-55-21: removed process groupkube-controller-manager-55-22: added process groupkube-scheduler-55-22: added process group[root@cfzx55-22 ~]#[root@cfzx55-22 ~]# supervisorctl statusetcd-server-55-22 RUNNING pid 1013, uptime 5:25:59kube-apiserver-55-22 RUNNING pid 1012, uptime 5:25:59kube-controller-manager-55-22 RUNNING pid 3234, uptime 0:00:32kube-scheduler-55-22 RUNNING pid 3187, uptime 0:03:19[root@cfzx55-22 ~]# netstat -luntp | grep kubetcp 0 0 0.0.0.0:6443 0.0.0.0:* LISTEN 1014/./kube-apiservtcp 0 0 127.0.0.1:10252 0.0.0.0:* LISTEN 3235/./kube-controltcp 0 0 0.0.0.0:10259 0.0.0.0:* LISTEN 3189/./kube-schedul[root@cfzx55-22 ~]#部署22上的kube-controller-manager时，没有修改名称。
查看集群状态
[root@cfzx55-22 bin]# kubectl get csWarning: v1 ComponentStatus is deprecated in v1.19+NAME STATUS MESSAGE ERRORcontroller-manager Healthy okscheduler Healthy oketcd-2 Healthy {"health":"true","reason":""}etcd-0 Healthy {"health":"true","reason":""}etcd-1 Healthy {"health":"true","reason":""}[root@cfzx55-22 bin]#查看集群资源
[root@cfzx55-21 ~]# kubectl get sa -ANAMESPACE NAME SECRETS AGEdefault default 1 114mkube-node-lease default 1 114mkube-public default 1 114mkube-system attachdetach-controller 1 116mkube-system bootstrap-signer 1 114mkube-system certificate-controller 1 116mkube-system clusterrole-aggregation-controller 1 114mkube-system cronjob-controller 1 116mkube-system daemon-set-controller 1 116mkube-system default 1 114mkube-system deployment-controller 1 116mkube-system disruption-controller 1 116mkube-system endpoint-controller 1 114mkube-system endpointslice-controller 1 116mkube-system endpointslicemirroring-controller 1 116mkube-system ephemeral-volume-controller 1 116mkube-system expand-controller 1 114mkube-system generic-garbage-collector 1 114mkube-system horizontal-pod-autoscaler 1 116mkube-system job-controller 1 116mkube-system namespace-controller 1 116mkube-system node-controller 1 116mkube-system persistent-volume-binder 1 114mkube-system pod-garbage-collector 1 114mkube-system pv-protection-controller 1 114mkube-system pvc-protection-controller 1 114mkube-system replicaset-controller 1 116mkube-system replication-controller 1 114mkube-system resourcequota-controller 1 114mkube-system root-ca-cert-publisher 1 116mkube-system service-account-controller 1 116mkube-system service-controller 1 116mkube-system statefulset-controller 1 116mkube-system token-cleaner 1 114mkube-system ttl-after-finished-controller 1 114mkube-system ttl-controller 1 116m[root@cfzx55-21 ~]# kubectl get ns -ANAME STATUS AGEdefault Active 15hkube-node-lease Active 15hkube-public Active 15hkube-system Active 15h[root@cfzx55-21 ~]# kubectl get role -ANAMESPACE NAME CREATED ATkube-public system:controller:bootstrap-signer 2022-03-12T14:36:17Zkube-system extension-apiserver-authentication-reader 2022-03-12T14:36:16Zkube-system system::leader-locking-kube-controller-manager 2022-03-12T14:36:16Zkube-system system::leader-locking-kube-scheduler 2022-03-12T14:36:16Zkube-system system:controller:bootstrap-signer 2022-03-12T14:36:16Zkube-system system:controller:cloud-provider 2022-03-12T14:36:16Zkube-system system:controller:token-cleaner 2022-03-12T14:36:16Z[root@cfzx55-21 ~]#至此，Master节点部署完成。