前文环境中完成部署ETCD集群+Flannel网络,实现容器间通信,本文基于二进制部署单master节点集群。前文链接地址:Kubernetes------二进制部署ETCD集群+Flannel网络
文章目录
一、K8S单master节点集群架构
二、master节点部署
2.1、生成证书
创建k8s工作目录和apiserver证书目录
[root@master1 ~/k8s]# mkdir -p /opt/kubernetes/{cfg,bin,ssl}
[root@master1 ~/k8s]# mkdir k8s-cert
生成证书
[root@master1 ~/k8s]# cd k8s-cert/
[root@master1 ~/k8s/k8s-cert]# rz -E
rz waiting to receive.
[root@master1 ~/k8s/k8s-cert]# ls
k8s-cert.sh
[root@localhost k8s-cert]# cat k8s-cert.sh
cat > ca-config.json <<EOF
{
"signing": {
"default": {
"expiry": "87600h"
},
"profiles": {
"kubernetes": {
"expiry": "87600h",
"usages": [
"signing",
"key encipherment",
"server auth",
"client auth"
]
}
}
}
}
EOF
cat > ca-csr.json <<EOF
{
"CN": "kubernetes",
"key": {
"algo": "rsa",
"size": 2048
},
"names": [
{
"C": "CN",
"L": "Beijing",
"ST": "Beijing",
"O": "k8s",
"OU": "System"
}
]
}
EOF
cfssl gencert -initca ca-csr.json | cfssljson -bare ca -
#-----------------------
cat > server-csr.json <<EOF
{
"CN": "kubernetes",
"hosts": [
"10.0.0.1",
"127.0.0.1",
"192.168.88.10", #master1节点
"192.168.88.40", #master2节点(多master节点集群需要)
"192.168.88.100", #VIP飘逸地址
"192.168.88.50", #nginx1负载均衡地址(主)
"192.168.88.60", #nginx2负载均衡地址(备)
"kubernetes",
"kubernetes.default",
"kubernetes.default.svc",
"kubernetes.default.svc.cluster",
"kubernetes.default.svc.cluster.local"
],
"key": {
"algo": "rsa",
"size": 2048
},
"names": [
{
"C": "CN",
"L": "BeiJing",
"ST": "BeiJing",
"O": "k8s",
"OU": "System"
}
]
}
EOF
cfssl gencert -ca=ca.pem -ca-key=ca-key.pem -config=ca-config.json -profile=kubernetes server-csr.json | cfssljson -bare server
#-----------------------
cat > admin-csr.json <<EOF
{
"CN": "admin",
"hosts": [],
"key": {
"algo": "rsa",
"size": 2048
},
"names": [
{
"C": "CN",
"L": "BeiJing",
"ST": "BeiJing",
"O": "system:masters",
"OU": "System"
}
]
}
EOF
cfssl gencert -ca=ca.pem -ca-key=ca-key.pem -config=ca-config.json -profile=kubernetes admin-csr.json | cfssljson -bare admin
#-----------------------
cat > kube-proxy-csr.json <<EOF
{
"CN": "system:kube-proxy",
"hosts": [],
"key": {
"algo": "rsa",
"size": 2048
},
"names": [
{
"C": "CN",
"L": "BeiJing",
"ST": "BeiJing",
"O": "k8s",
"OU": "System"
}
]
}
EOF
cfssl gencert -ca=ca.pem -ca-key=ca-key.pem -config=ca-config.json -profile=kubernetes kube-proxy-csr.json | cfssljson -bare kube-proxy
生成k8s证书文件
[root@master1 ~/k8s/k8s-cert]# bash k8s-cert.sh
2021/10/11 10:20:02 [INFO] generating a new CA key and certificate from CSR
2021/10/11 10:20:02 [INFO] generate received request
2021/10/11 10:20:02 [INFO] received CSR
2021/10/11 10:20:02 [INFO] generating key: rsa-2048
2021/10/11 10:20:02 [INFO] encoded CSR
2021/10/11 10:20:02 [INFO] signed certificate with serial number 679512443905223183200237478752811398815110474327
2021/10/11 10:20:02 [INFO] generate received request
2021/10/11 10:20:02 [INFO] received CSR
2021/10/11 10:20:02 [INFO] generating key: rsa-2048
2021/10/11 10:20:03 [INFO] encoded CSR
2021/10/11 10:20:03 [INFO] signed certificate with serial number 234172399787405542945824847826011723780133550292
2021/10/11 10:20:03 [WARNING] This certificate lacks a "hosts" field. This makes it unsuitable for
websites. For more information see the Baseline Requirements for the Issuance and Management
of Publicly-Trusted Certificates, v.1.1.6, from the CA/Browser Forum (https://cabforum.org);
specifically, section 10.2.3 ("Information Requirements").
2021/10/11 10:20:03 [INFO] generate received request
2021/10/11 10:20:03 [INFO] received CSR
2021/10/11 10:20:03 [INFO] generating key: rsa-2048
2021/10/11 10:20:03 [INFO] encoded CSR
2021/10/11 10:20:03 [INFO] signed certificate with serial number 238562792074161659481987252101976292233447142560
2021/10/11 10:20:03 [WARNING] This certificate lacks a "hosts" field. This makes it unsuitable for
websites. For more information see the Baseline Requirements for the Issuance and Management
of Publicly-Trusted Certificates, v.1.1.6, from the CA/Browser Forum (https://cabforum.org);
specifically, section 10.2.3 ("Information Requirements").
2021/10/11 10:20:03 [INFO] generate received request
2021/10/11 10:20:03 [INFO] received CSR
2021/10/11 10:20:03 [INFO] generating key: rsa-2048
2021/10/11 10:20:03 [INFO] encoded CSR
2021/10/11 10:20:03 [INFO] signed certificate with serial number 145115630940299886538335417826109416531097137173
2021/10/11 10:20:03 [WARNING] This certificate lacks a "hosts" field. This makes it unsuitable for
websites. For more information see the Baseline Requirements for the Issuance and Management
of Publicly-Trusted Certificates, v.1.1.6, from the CA/Browser Forum (https://cabforum.org);
specifically, section 10.2.3 ("Information Requirements").
[root@master1 ~/k8s/k8s-cert]# ls
admin.csr admin-key.pem ca-config.json ca-csr.json ca.pem kube-proxy.csr kube-proxy-key.pem server.csr server-key.pem
admin-csr.json admin.pem ca.csr ca-key.pem k8s-cert.sh kube-proxy-csr.json kube-proxy.pem server-csr.json server.pem
[root@master1 ~/k8s/k8s-cert]# ls *.pem
admin-key.pem admin.pem ca-key.pem ca.pem kube-proxy-key.pem kube-proxy.pem server-key.pem server.pem
把ca server端证书复制到k8s工作目录ssl下
[root@master1 ~/k8s/k8s-cert]# cp ca*.pem server*.pem /opt/kubernetes/ssl
[root@master1 ~/k8s/k8s-cert]# ls /opt/kubernetes/ssl/
ca-key.pem ca.pem server-key.pem server.pem
2.2、生成token(令牌)并绑定角色(bootstrap)
导入kubernetes软件包并解压
[root@master1 ~/k8s/k8s-cert]# cd ..
[root@master1 ~/k8s]# rz -E
rz waiting to receive.
[root@master1 ~/k8s]# ls
etcd-cert etcd.sh etcd-v3.3.10-linux-amd64 etcd-v3.3.10-linux-amd64.tar.gz flannel-v0.10.0-linux-amd64.tar.gz k8s-cert kubernetes-server-linux-amd64.tar.gz
[root@master1 ~/k8s]# tar zxvf kubernetes-server-linux-amd64.tar.gz
[root@master1 ~/k8s]# ls
etcd-cert etcd.sh etcd-v3.3.10-linux-amd64 etcd-v3.3.10-linux-amd64.tar.gz flannel-v0.10.0-linux-amd64.tar.gz k8s-cert kubernetes kubernetes-server-linux-amd64.tar.gz
[root@master1 ~/k8s]# cd kubernetes/
[root@master1 ~/k8s/kubernetes]# ls
addons kubernetes-src.tar.gz LICENSES server
[root@master1 ~/k8s/kubernetes]# cd server/
[root@master1 ~/k8s/kubernetes/server]# ls
bin
[root@master1 ~/k8s/kubernetes/server]# cd bin/
[root@master1 ~/k8s/kubernetes/server/bin]# ls
apiextensions-apiserver cloud-controller-manager.tar kube-apiserver kube-controller-manager kubectl kube-proxy.docker_tag kube-scheduler.docker_tag
cloud-controller-manager hyperkube kube-apiserver.docker_tag kube-controller-manager.docker_tag kubelet kube-proxy.tar kube-scheduler.tar
cloud-controller-manager.docker_tag kubeadm kube-apiserver.tar kube-controller-manager.tar kube-proxy kube-scheduler mounter
#master、node节点所有组件都在bin目录中
复制master节点命令到k8s工作目录
[root@master1 ~/k8s/kubernetes/server/bin]# cp kube-controller-manager kubectl kube-apiserver kube-scheduler /opt/kubernetes/bin
[root@master1 ~/k8s/kubernetes/server/bin]# ls /opt/kubernetes/bin/
kube-apiserver kube-controller-manager kubectl kube-scheduler
随机生成序列号
[root@master1 ~/k8s/kubernetes/server/bin]# head -c 16 /dev/urandom | od -An -t x | tr -d ' '
6e619888b46fb4bcd84e31558db0851e
编辑token(令牌)文件
[root@master1 ~/k8s/kubernetes/server/bin]# cd /opt/kubernetes/cfg/
[root@master1 /opt/kubernetes/cfg]# ls
[root@master1 /opt/kubernetes/cfg]# vim token.csv
[root@master1 /opt/kubernetes/cfg]# cat token.csv
6e619888b46fb4bcd84e31558db0851e,kubelet-bootstrap,10001,"system:kubelet-bootstrap"
2.3、开启master节点相关服务
2.3.1、开启apiserver服务
导入master.sh软件包并解压
[root@master1 /opt/kubernetes/cfg]# cd
[root@master1 ~]# cd k8s/
[root@master1 ~/k8s]# rz -E
rz waiting to receive.
[root@master1 ~/k8s]# ls
etcd-cert etcd.sh etcd-v3.3.10-linux-amd64 etcd-v3.3.10-linux-amd64.tar.gz flannel-v0.10.0-linux-amd64.tar.gz k8s-cert kubernetes kubernetes-server-linux-amd64.tar.gz master.zip
[root@master1 ~/k8s]# unzip master.zip
Archive: master.zip
inflating: apiserver.sh
inflating: controller-manager.sh
inflating: scheduler.sh
[root@master1 ~/k8s]# ls
apiserver.sh etcd-cert etcd-v3.3.10-linux-amd64 flannel-v0.10.0-linux-amd64.tar.gz kubernetes master.zip
controller-manager.sh etcd.sh etcd-v3.3.10-linux-amd64.tar.gz k8s-cert kubernetes-server-linux-amd64.tar.gz scheduler.sh
[root@master1 ~/k8s]# chmod +x controller-manager.sh
[root@master1 ~/k8s]# ls
apiserver.sh etcd-cert etcd-v3.3.10-linux-amd64 flannel-v0.10.0-linux-amd64.tar.gz kubernetes master.zip
controller-manager.sh etcd.sh etcd-v3.3.10-linux-amd64.tar.gz k8s-cert kubernetes-server-linux-amd64.tar.gz scheduler.sh
查看apiserver.sh文件
[root@master1 ~/k8s]# cat apiserver.sh
#!/bin/bash
MASTER_ADDRESS=$1 #本地地址
ETCD_SERVERS=$2 #群集
cat <<EOF >/opt/kubernetes/cfg/kube-apiserver #生成配置文件到k8s工作目录
KUBE_APISERVER_OPTS="--logtostderr=true \\ #从ETCD读取、存入数据
--v=4 \\
--etcd-servers=${ETCD_SERVERS} \\
--bind-address=${MASTER_ADDRESS} \\ #绑定地址
--secure-port=6443 \\
--advertise-address=${MASTER_ADDRESS} \\ #master本地地址
--allow-privileged=true \\ #允许授权
--service-cluster-ip-range=10.0.0.0/24 \\
--enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,ResourceQuota,NodeRestriction \\ #plugin插件,包括命名空间中的插件、server端的授权
--authorization-mode=RBAC,Node \\ #使用RBAC模式验证node端
--kubelet-https=true \\ #允许对方使用https协议进行访问
--enable-bootstrap-token-auth \\ #开启bootstrap令牌授权
--token-auth-file=/opt/kubernetes/cfg/token.csv \\ #令牌文件路径
--service-node-port-range=30000-50000 \\ #开启的监听端口
#以下均为证书文件
--tls-cert-file=/opt/kubernetes/ssl/server.pem \\
--tls-private-key-file=/opt/kubernetes/ssl/server-key.pem \\
--client-ca-file=/opt/kubernetes/ssl/ca.pem \\
--service-account-key-file=/opt/kubernetes/ssl/ca-key.pem \\
--etcd-cafile=/opt/etcd/ssl/ca.pem \\
--etcd-certfile=/opt/etcd/ssl/server.pem \\
--etcd-keyfile=/opt/etcd/ssl/server-key.pem"
EOF
cat <<EOF >/usr/lib/systemd/system/kube-apiserver.service #服务启动脚本
[Unit]
Description=Kubernetes API Server
Documentation=https://github.com/kubernetes/kubernetes
[Service]
EnvironmentFile=-/opt/kubernetes/cfg/kube-apiserver
ExecStart=/opt/kubernetes/bin/kube-apiserver \$KUBE_APISERVER_OPTS
Restart=on-failure
[Install]
WantedBy=multi-user.target
EOF
systemctl daemon-reload
systemctl enable kube-apiserver
systemctl restart kube-apiserver
开启apiserver服务
[root@master1 ~/k8s]# bash apiserver.sh 192.168.88.10 https://192.168.88.10:2379,https://192.168.88.20:2379,https://192.168.88.30:2379
Created symlink from /etc/systemd/system/multi-user.target.wants/kube-apiserver.service to /usr/lib/systemd/system/kube-apiserver.service.
#查看api进程验证启动状态
[root@master1 ~/k8s]# ps aux | grep kube
root 51738 55.7 17.1 436132 347928 ? Ssl 10:50 0:07 /opt/kubernetes/bin/kube-apiserver --logtostderr=true --v=4 --etcd-servers=https://192.168.88.10:2379,https://192.168.88.20:2379,https://192.168.88.30:2379 --bind-address=192.168.88.10 --secure-port=6443 --advertise-address=192.168.88.10 --allow-privileged=true --service-cluster-ip-range=10.0.0.0/24 --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,ResourceQuota,NodeRestriction --authorization-mode=RBAC,Node --kubelet-https=true --enable-bootstrap-token-auth --token-auth-file=/opt/kubrnetes/cfg/token.csv --service-node-port-range=30000-50000 --tls-cert-file=/opt/kubernetes/ssl/server.pem --tls-private-key-file=/opt/kubernetes/ssl/server-key.pem --client-ca-file=/opt/kubernetes/ssl/ca.pem --service-account-key-file=/opt/kubernetes/ssl/ca-key.pem --etcd-cafile=/opt/etcd/ssl/ca.pem --etcd-certfile=/opt/etcd/ssl/server.pem --etcd-keyfile=/opt/etcd/ssl/server-key.pem
root 51746 0.0 0.0 112676 972 pts/1 R+ 10:50 0:00 grep --color=auto kube
查看配置文件
[root@master1 ~/k8s]# cat /opt/kubernetes/cfg/kube-apiserver
KUBE_APISERVER_OPTS="--logtostderr=true \
--v=4 \
--etcd-servers=https://192.168.88.10:2379,https://192.168.88.20:2379,https://192.168.88.30:2379 \
--bind-address=192.168.88.10 \
--secure-port=6443 \
--advertise-address=192.168.88.10 \
--allow-privileged=true \
--service-cluster-ip-range=10.0.0.0/24 \
--enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,ResourceQuota,NodeRestriction \
--authorization-mode=RBAC,Node \
--kubelet-https=true \
--enable-bootstrap-token-auth \
--token-auth-file=/opt/kubernetes/cfg/token.csv \
--service-node-port-range=30000-50000 \
--tls-cert-file=/opt/kubernetes/ssl/server.pem \
--tls-private-key-file=/opt/kubernetes/ssl/server-key.pem \
--client-ca-file=/opt/kubernetes/ssl/ca.pem \
--service-account-key-file=/opt/kubernetes/ssl/ca-key.pem \
--etcd-cafile=/opt/etcd/ssl/ca.pem \
--etcd-certfile=/opt/etcd/ssl/server.pem \
--etcd-keyfile=/opt/etcd/ssl/server-key.pem"
查看服务状态
[root@master1 ~/k8s]# systemctl status kube-apiserver.service
● kube-apiserver.service - Kubernetes API Server
Loaded: loaded (/usr/lib/systemd/system/kube-apiserver.service; enabled; vendor preset: disabled)
Active: active (running) since 一 2021-10-11 10:50:40 CST; 7min ago
查看端口开启情况
[root@master1 ~/k8s]# netstat -natp | grep 6443
tcp 0 0 192.168.88.10:6443 0.0.0.0:* LISTEN 51738/kube-apiserve
tcp 0 0 192.168.88.10:59260 192.168.88.10:6443 ESTABLISHED 51738/kube-apiserve
tcp 0 0 192.168.88.10:6443 192.168.88.10:59260 ESTABLISHED 51738/kube-apiserve
2.3.2、开启scheduler服务
查看scheduler启动脚本
[root@master1 ~/k8s]# vim scheduler.sh
#!/bin/bash
MASTER_ADDRESS=$1
cat <<EOF >/opt/kubernetes/cfg/kube-scheduler
KUBE_SCHEDULER_OPTS="--logtostderr=true \\ #定义日志记录
--v=4 \\
--master=${MASTER_ADDRESS}:8080 \\ #定义master地址,指向8080端口
--leader-elect" #定位为leader
EOF
cat <<EOF >/usr/lib/systemd/system/kube-scheduler.service #定义启动脚本
[Unit]
Description=Kubernetes Scheduler
Documentation=https://github.com/kubernetes/kubernetes
[Service]
EnvironmentFile=-/opt/kubernetes/cfg/kube-scheduler
ExecStart=/opt/kubernetes/bin/kube-scheduler \$KUBE_SCHEDULER_OPTS
Restart=on-failure
[Install]
WantedBy=multi-user.target
EOF
systemctl daemon-reload
systemctl enable kube-scheduler
systemctl restart kube-scheduler
开启scheduler服务并查看服务状态
[root@master1 ~/k8s]# ./scheduler.sh 127.0.0.1
Created symlink from /etc/systemd/system/multi-user.target.wants/kube-scheduler.service to /usr/lib/systemd/system/kube-scheduler.service.
#查看进程
[root@master1 ~/k8s]# ps aux | grep sch
root 9 0.0 0.0 0 0 ? R 00:07 0:01 [rcu_sched]
root 51841 0.5 1.0 46416 21568 ? Ssl 10:55 0:00 /opt/kubernetes/bin/kube-scheduler --logtostderr=true --v=4 --master=127.0.0.1:8080 --leader-elect
root 51849 0.0 0.0 112680 972 pts/1 S+ 10:56 0:00 grep --color=auto sch
#查看服务状态
[root@master1 ~/k8s]# systemctl status kube-scheduler.service
● kube-scheduler.service - Kubernetes Scheduler
Loaded: loaded (/usr/lib/systemd/system/kube-scheduler.service; enabled; vendor preset: disabled)
Active: active (running) since 一 2021-10-11 10:55:30 CST; 1min 47s ago
2.3.3、开启controller-manager服务
#执行脚本文件
[root@master1 ~/k8s]# ./controller-manager.sh
Created symlink from /etc/systemd/system/multi-user.target.wants/kube-controller-manager.service to /usr/lib/systemd/system/kube-controller-manager.service.
#查看服务状态
[root@master1 ~/k8s]# systemctl status kube-controller-manager.service
● kube-controller-manager.service - Kubernetes Controller Manager
Loaded: loaded (/usr/lib/systemd/system/kube-controller-manager.service; enabled; vendor preset: disabled)
Active: active (running) since 一 2021-10-11 11:00:15 CST; 4s ago
2.3.4、查看master节点状态
[root@master1 ~/k8s]# /opt/kubernetes/bin/kubectl get cs
NAME STATUS MESSAGE ERROR
controller-manager Healthy ok
etcd-0 Healthy {"health":"true"}
etcd-1 Healthy {"health":"true"}
etcd-2 Healthy {"health":"true"}
scheduler Healthy ok
三、node节点部署
3.1、node1节点部署
把master节点kubelet、kube-proxy复制到node节点
[root@master1 ~/k8s]# cd kubernetes/server/bin/
[root@master1 ~/k8s/kubernetes/server/bin]# ls
apiextensions-apiserver cloud-controller-manager.tar kube-apiserver kube-controller-manager kubectl kube-proxy.docker_tag kube-scheduler.docker_tag
cloud-controller-manager hyperkube kube-apiserver.docker_tag kube-controller-manager.docker_tag kubelet kube-proxy.tar kube-scheduler.tar
cloud-controller-manager.docker_tag kubeadm kube-apiserver.tar kube-controller-manager.tar kube-proxy kube-scheduler mounter
[root@master1 ~/k8s/kubernetes/server/bin]# scp kubelet kube-proxy root@192.168.88.20:/opt/kubernetes/bin/
root@192.168.88.20's password:
kubelet 100% 168MB 125.2MB/s 00:01
kube-proxy 100% 48MB 89.1MB/s 00:00
[root@master1 ~/k8s/kubernetes/server/bin]# scp kubelet kube-proxy root@192.168.88.30:/opt/kubernetes/bin/
root@192.168.88.30's password:
kubelet 100% 168MB 134.6MB/s 00:01
kube-proxy 100% 48MB 134.8MB/s 00:00
node节点导入node.zip并解压
[root@node1 ~]# rz -E
rz waiting to receive.
[root@node1 ~]# ls
anaconda-ks.cfg flannel.sh flannel-v0.10.0-linux-amd64.tar.gz initial-setup-ks.cfg node.zip README.md 公共 模板 视频 图片 文档 下载 音乐 桌面
[root@node1 ~]# unzip node.zip
Archive: node.zip
inflating: proxy.sh
inflating: kubelet.sh
[root@node1 ~]# ls
anaconda-ks.cfg flannel.sh flannel-v0.10.0-linux-amd64.tar.gz initial-setup-ks.cfg kubelet.sh node.zip proxy.sh README.md 公共 模板 视频 图片 文档 下载 音乐 桌面
master节点进行kube配置(master与node节点通讯前提)
[root@master1 ~/k8s]# mkdir kubeconfig
[root@master1 ~/k8s]# cd kubeconfig/
[root@master1 ~/k8s/kubeconfig]# rz -E
rz waiting to receive.
[root@master1 ~/k8s/kubeconfig]# ls
kubeconfig.sh
[root@master1 ~/k8s/kubeconfig]# mv kubeconfig.sh kubeconfig
[root@master1 ~/k8s/kubeconfig]# vim kubeconfig
设置环境变量
[root@master1 ~/k8s/kubeconfig]# vim /etc/profile
export PATH=$PATH:/opt/kubernetes/bin/
[root@master1 ~/k8s/kubeconfig]# source /etc/profile
#设置完成后,即可使用kubectl命令
root@master1 ~/k8s/kubeconfig]# kubectl get cs
NAME STATUS MESSAGE ERROR
scheduler Healthy ok
controller-manager Healthy ok
etcd-0 Healthy {"health":"true"}
etcd-2 Healthy {"health":"true"}
etcd-1 Healthy {"health":"true"}
执行kubeconfig脚本
[root@master1 ~/k8s/kubeconfig]# bash kubeconfig 192.168.88.10 /root/k8s/k8s-cert/
Cluster "kubernetes" set.
User "kubelet-bootstrap" set.
Context "default" created.
Switched to context "default".
Cluster "kubernetes" set.
User "kube-proxy" set.
Context "default" created.
Switched to context "default".
#生成两个配置文件
[root@master1 ~/k8s/kubeconfig]# ls
bootstrap.kubeconfig kubeconfig kube-proxy.kubeconfig token.csv
拷贝生成的两个配置文件(与master节点通信和被master节点控制)到node节点
[root@master1 ~/k8s/kubeconfig]# scp bootstrap.kubeconfig kube-proxy.kubeconfig root@192.168.88.20:/opt/kubernetes/cfg/
root@192.168.88.20's password:
bootstrap.kubeconfig 100% 2167 2.6MB/s 00:00
kube-proxy.kubeconfig 100% 6273 4.6MB/s 00:00
[root@master1 ~/k8s/kubeconfig]# scp bootstrap.kubeconfig kube-proxy.kubeconfig root@192.168.88.30:/opt/kubernetes/cfg/
root@192.168.88.30's password:
bootstrap.kubeconfig 100% 2167 2.3MB/s 00:00
kube-proxy.kubeconfig 100% 6273 3.4MB/s 00:00
[root@node1 ~]# ls /opt/kubernetes/cfg/
bootstrap.kubeconfig flanneld kube-proxy.kubeconfig
创建bootstrap角色,并赋予权限用于连接apiserver请求签名
[root@master1 ~/k8s/kubeconfig]# kubectl create clusterrolebinding kubelet-bootstrap --clusterrole=system:node-bootstrapper --user=kubelet-bootstrap
clusterrolebinding.rbac.authorization.k8s.io/kubelet-bootstrap created
##添加完成后,master节点管理node节点需要通过bootstrap角色
node1节点执行kubelet脚本,用于请求连接master节点
[root@node1 ~]# bash kubelet.sh 192.168.88.20
Created symlink from /etc/systemd/system/multi-user.target.wants/kubelet.service to /usr/lib/systemd/system/kubelet.service.
#查看kubelet进程
[root@node1 ~]# ps aux | grep kubelet
root 9219 1.9 2.4 308324 48820 ? Ssl 11:01 0:00 /opt/kubernetes/bin/kubelet --logtostderr=true --v=4 --hostname-override=192.168.88.20 --kubeconfig=/opt/kubernetes/cfg/kubelet.kubeconfig --bootstrap-kubeconfig=/opt/kubernetes/cfg/bootstrap.kubeconfig --config=/opt/kubernetes/cfg/kubelet.config --cert-dir=/opt/kubernetes/ssl --pod-infra-container-image=registry.cn-hangzhou.aliyuncs.com/google-containers/pause-amd64:3.0
root 9283 0.0 0.0 112676 980 pts/1 R+ 11:02 0:00 grep --color=auto kubelet
#查看服务状态
systemctl status kubelet.service
#此时,master在node节点上的kubelet代理已完成
master节点检查node1节点请求
[root@master1 ~/k8s/kubeconfig]# kubectl get csr
NAME AGE REQUESTOR CONDITION
node-csr-6nS_azIgEBxDWLjUEuzPl8V7nfSDF_2uk6okI6CKp8s 3m11s kubelet-bootstrap Pending
#pending为请求状态(等待集群给该节点颁发证书)
颁发证书
[root@master1 ~/k8s/kubeconfig]# kubectl certificate approve node-csr-6nS_azIgEBxDWLjUEuzPl8V7nfSDF_2uk6okI6CKp8s
certificatesigningrequest.certificates.k8s.io/node-csr-6nS_azIgEBxDWLjUEuzPl8V7nfSDF_2uk6okI6CKp8s approved
#再次查看
[root@master1 ~/k8s/kubeconfig]# kubectl get csr
NAME AGE REQUESTOR CONDITION
node-csr-6nS_azIgEBxDWLjUEuzPl8V7nfSDF_2uk6okI6CKp8s 4m48s kubelet-bootstrap Approved,Issued
#状态变为Approved,Issued(允许加入集群)
#查看集群节点
[root@master1 ~/k8s/kubeconfig]# kubectl get nodes
NAME STATUS ROLES AGE VERSION
192.168.88.20 Ready <none> 81s v1.12.3
node1节点开启proxy代理服务
3.2、node2节点部署
把node1节点/opt/kubernetes工作目录及启动脚本复制到node2节点
修改node2配置文件
删除复制过来的证书,node2节点会自动申请证书。并修改配置文件(kubelet、kubelet.confg、kube-proxy)
#删除所有证书文件
[root@node2 ~]# cd /opt/kubernetes/ssl/
[root@node2 /opt/kubernetes/ssl]# ls
kubelet-client-2021-10-15-11-05-58.pem kubelet-client-current.pem kubelet.crt kubelet.key
[root@node2 /opt/kubernetes/ssl]# rm -rf *
[root@node2 /opt/kubernetes/ssl]# ls
[root@node2 /opt/kubernetes/ssl]#
修改kubelet配置文件
[root@node2 /opt/kubernetes/ssl]# cd ..
[root@node2 /opt/kubernetes]# cd cfg/
[root@node2 /opt/kubernetes/cfg]# ls
bootstrap.kubeconfig flanneld kubelet kubelet.config kubelet.kubeconfig kube-proxy kube-proxy.kubeconfig
[root@node2 /opt/kubernetes/cfg]# vim kubelet
KUBELET_OPTS="--logtostderr=true \
--v=4 \
--hostname-override=192.168.88.30 \ #改为node2 IP地址
--kubeconfig=/opt/kubernetes/cfg/kubelet.kubeconfig \
--bootstrap-kubeconfig=/opt/kubernetes/cfg/bootstrap.kubeconfig \
--config=/opt/kubernetes/cfg/kubelet.config \
--cert-dir=/opt/kubernetes/ssl \
--pod-infra-container-image=registry.cn-hangzhou.aliyuncs.com/google-containers/pause-amd64:3.0"
修改kubelet.conf配置文件
[root@node2 /opt/kubernetes/cfg]# vim kubelet.config
kind: KubeletConfiguration
apiVersion: kubelet.config.k8s.io/v1beta1
address: 192.168.88.30 #改为node2 IP地址
port: 10250
readOnlyPort: 10255
cgroupDriver: cgroupfs
clusterDNS:
- 10.0.0.2
clusterDomain: cluster.local.
failSwapOn: false
authentication:
anonymous:
enabled: true
修改kube-proxy配置文件
root@node2 /opt/kubernetes/cfg]# vim kube-proxy
KUBE_PROXY_OPTS="--logtostderr=true \
--v=4 \
--hostname-override=192.168.88.30 \ #改为node2 IP地址
--cluster-cidr=10.0.0.0/24 \
--proxy-mode=ipvs \
--kubeconfig=/opt/kubernetes/cfg/kube-proxy.kubeconfig"
开启kubelet服务
[root@node2 /opt/kubernetes/cfg]# systemctl start kubelet
[root@node2 /opt/kubernetes/cfg]# systemctl enable kubelet
Created symlink from /etc/systemd/system/multi-user.target.wants/kubelet.service to /usr/lib/systemd/system/kubelet.service.
#kubelet 启动成功后会向master发出加入集群请求,稍后在master节点查看、授权即可
master节点对node2节点进行授权
[root@master1 ~/k8s/kubeconfig]# kubectl get csr
NAME AGE REQUESTOR CONDITION
node-csr-6nS_azIgEBxDWLjUEuzPl8V7nfSDF_2uk6okI6CKp8s 19m kubelet-bootstrap Approved,Issued
node-csr-T8wLSDre6Dsh84f0_rvYJ9CgkU4bbszs0cFIpUliOOU 65s kubelet-bootstrap Pending
#授权
[root@master1 ~/k8s/kubeconfig]# kubectl certificate approve node-csr-T8wLSDre6Dsh84f0_rvYJ9CgkU4bbszs0cFIpUliOOU
certificatesigningrequest.certificates.k8s.io/node-csr-T8wLSDre6Dsh84f0_rvYJ9CgkU4bbszs0cFIpUliOOU approved
查看集群状态
[root@master1 ~/k8s/kubeconfig]# kubectl get nodes
NAME STATUS ROLES AGE VERSION
192.168.88.20 Ready <none> 16m v1.12.3
192.168.88.30 Ready <none> 54s v1.12.3