k8s二进制部署（高可用）+云服务器LB转发
·
K8S高可用集群二进制部署全程
1环境准备
环境准备:
主机名： IP地址 角色划分
apiserver-lb 10.0.250.2 为负载均衡外部访问入口
master01 10.0.250.3 api-server，control manager，scheduler，etcd
master02 10.0.250.4 api-server，control manager，scheduler，etcd
master03 10.0.250.5 api-server，control manager，scheduler，etcd
worker01 10.0.250.6 kubelet，kube-proxy
worker02 10.0.250.7 kubelet，kube-proxy
硬件配置:
2c 2G
K8S集群各主机环境准备
1.所有节点安装常用的软件包
删除自动更新（可选）
PKG_NAME="unattended-upgrades"; PID=$(ps aux | grep $PKG_NAME | grep -v grep | awk '{print $2}'); [ -n "$PID" ] && sudo kill -9 $PID; sudo rm -f /var/lib/dpkg/lock-frontend /var/lib/dpkg/lock /var/cache/apt/archives/lock; sudo dpkg --configure -a; sudo apt purge -y $PKG_NAME && sudo apt autoremove -y && sudo apt clean
apt update
apt -y install bind9-utils expect rsync jq psmisc net-tools lvm2 vim unzip rename
2主机名及hosts文件解析
2.2 设置相应的主机名及hosts文件解析
cat >> /etc/hosts << EOF
10.0.250.2 apiserver-lb
10.0.250.3 master01
10.0.250.4 master02
10.0.250.5 master03
10.0.250.6 worker01
10.0.250.7 worker02
EOF
2.3 配置免密码登录其他节点
cat > password_free_login.sh <<'EOF'
#!/bin/bash
# 创建密钥对
ssh-keygen -t rsa -P "" -f /root/.ssh/id_rsa -q
# 声明你服务器密码，建议所有节点的密码均一致，否则该脚本需要再次进行优化
export mypasswd=wlw123456..
# 定义主机列表
k8s_host_list=(master02 master03 worker01 worker02)
# 配置免密登录，利用expect工具免交互输入
for i in ${k8s_host_list[@]};do
expect -c "
spawn ssh-copy-id -i /root/.ssh/id_rsa.pub root@$i
expect {
\"*yes/no*\" {send \"yes\r\"; exp_continue}
\"*password*\" {send \"$mypasswd\r\"; exp_continue}
}"
done
EOF
bash password_free_login.sh
2.4 编写同步脚本
[root@master01 ~]# cat > /usr/local/sbin/data_rsync.sh <<'EOF'
#!/bin/bash
if [ $# -lt 1 ];then
echo "Usage: $0 /path/to/file(绝对路径) [mode: m|w]"
exit
fi
if [ ! -e $1 ];then
echo "[ $1 ] dir or file not find!"
exit
fi
fullpath=`dirname $1`
basename=`basename $1`
cd $fullpath
case $2 in
WORKER_NODE|w)
K8S_NODE=(master02 master03 worker01 worker02)
;;
MASTER_NODE|m)
K8S_NODE=(master02 master03)
;;
*)
K8S_NODE=(master02 master03 worker01 worker02)
;;
esac
for host in ${K8S_NODE[@]};do
tput setaf 2
echo ===== rsyncing ${host}: $basename =====
tput setaf 7
rsync -az $basename `whoami`@${host}:$fullpath
if [ $? -eq 0 ];then
echo "命令执行成功!"
fi
done
EOF
[root@master01 ~]# chmod +x /usr/local/sbin/data_rsync.sh
2.5 同步"/etc/hosts"文件到集群
[root@master01 ~]# data_rsync.sh /etc/hosts
如果链接不了
vim /etc/ssh/sshd_config
...
PubkeyAuthentication yes
AuthorizedKeysFile .ssh/authorized_keys
...
systemctl restart sshd
以及.ssh权限问题
root@master01:~# ll -d .ssh
drwx------ 2 root root 4096 Jan 2 11:09 .ssh/
root@master01:~# ll .ssh
total 24
drwx------ 2 root root 4096 Jan 2 11:09 ./
drwx------ 5 root root 4096 Jan 2 11:15 ../
-rw------- 1 root root 2602 Jan 2 11:09 id_rsa
-rw-r--r-- 1 root root 567 Jan 2 11:09 id_rsa.pub
-rw------- 1 root root 3912 Jan 2 11:09 known_hosts
-rw------- 1 root root 3076 Jan 2 11:09 known_hosts.old
root@master02:~# ll .ssh
total 12
drwx------ 2 root root 4096 Jan 2 11:09 ./
drwx------ 5 root root 4096 Jan 2 11:17 ../
-rw------- 1 root root 567 Jan 2 11:09 authorized_keys
root@master02:~# ll -d .ssh
drwx------ 2 root root 4096 Jan 2 11:09 .ssh/
root@master02:~#
3 系统优化
3.所有节点Linux基础环境优化
3.1 所有节点关闭NetworkManager，ufw
systemctl disable --now NetworkManager ufw
3.2 所有节点关闭swap分区，fstab注释swap
swapoff -a && sysctl -w vm.swappiness=0
sed -ri '/^[^#]*swap/s@^@#@' /etc/fstab
3.3 手动同步时区和时间
ln -svf /usr/share/zoneinfo/Asia/Shanghai /etc/localtime
3.4 所有节点配置limit
cat >> /etc/security/limits.conf <<'EOF'
* soft nofile 655360
* hard nofile 131072
* soft nproc 655350
* hard nproc 655350
* soft memlock unlimited
* hard memlock unlimited
EOF
3.5.所有节点优化sshd服务
sed -i 's@#UseDNS yes@UseDNS no@g' /etc/ssh/sshd_config
sed -i 's@^GSSAPIAuthentication yes@GSSAPIAuthentication no@g' /etc/ssh/sshd_config
- UseDNS选项:
打开状态下，当客户端试图登录SSH服务器时，服务器端先根据客户端的IP地址进行DNS PTR反向查询出客户端的主机名，然后根据查询出的客户端主机名进行DNS正向A记录查询，验证与其原始IP地址是否一致，这是防止客户端欺骗的一种措施，但一般我们的是动态IP不会有PTR记录，打开这个选项不过是在白白浪费时间而已，不如将其关闭。
- GSSAPIAuthentication:
当这个参数开启（ GSSAPIAuthentication yes ）的时候，通过SSH登陆服务器时候会有些会很慢！这是由于服务器端启用了GSSAPI。登陆的时候客户端需要对服务器端的IP地址进行反解析，如果服务器的IP地址没有配置PTR记录，那么就容易在这里卡住了。
3.6.Linux内核调优
cat > /etc/sysctl.d/k8s.conf <<'EOF'
# 以下3个参数是containerd所依赖的内核参数
net.ipv4.ip_forward = 1
net.bridge.bridge-nf-call-iptables = 1
net.bridge.bridge-nf-call-ip6tables = 1
net.ipv6.conf.all.disable_ipv6 = 1
fs.may_detach_mounts = 1
vm.overcommit_memory=1
vm.panic_on_oom=0
fs.inotify.max_user_watches=89100
fs.file-max=52706963
fs.nr_open=52706963
net.netfilter.nf_conntrack_max=2310720
net.ipv4.tcp_keepalive_time = 600
net.ipv4.tcp_keepalive_probes = 3
net.ipv4.tcp_keepalive_intvl =15
net.ipv4.tcp_max_tw_buckets = 36000
net.ipv4.tcp_tw_reuse = 1
net.ipv4.tcp_max_orphans = 327680
net.ipv4.tcp_orphan_retries = 3
net.ipv4.tcp_syncookies = 1
net.ipv4.tcp_max_syn_backlog = 16384
net.ipv4.ip_conntrack_max = 65536
net.ipv4.tcp_max_syn_backlog = 16384
net.ipv4.tcp_timestamps = 0
net.core.somaxconn = 16384
EOF
sysctl --system
3.7 修改终端颜色[可选]
cat <<EOF >> ~/.bashrc
PS1='[\[\e[34;1m\]\u@\[\e[0m\]\[\e[32;1m\]\H\[\e[0m\]\[\e[31;1m\] \W\[\e[0m\]]# '
EOF
source ~/.bashrc
4所有节点安装ipvsadm以实现kube-proxy的负载均衡
4.1 安装ipvsadm等相关工具
apt update -y
apt -y install ipvsadm ipset sysstat conntrack libseccomp2
4.2 所有节点创建要开机自动加载的模块配置文件
cat > /etc/modules-load.d/ipvs.conf << 'EOF'
ip_vs
ip_vs_lc
ip_vs_wlc
ip_vs_rr
ip_vs_wrr
ip_vs_lblc
ip_vs_lblcr
ip_vs_dh
ip_vs_sh
ip_vs_fo
ip_vs_nq
ip_vs_sed
ip_vs_ftp
ip_vs_sh
nf_conntrack
ip_tables
ip_set
xt_set
ipt_set
ipt_rpfilter
ipt_REJECT
ipip
EOF
4.3 修改ens33网卡名称为eth0【选做，建议修改】
4.3.1 修改配置文件
vim /etc/default/grub
...
GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0"
4.3.2 用grub2-mkconfig重新生成配置
grub-mkconfig -o /boot/grub/grub.cfg
4.3.3 修改网卡配置
[root@master01 ~]# cat /etc/netplan/00-installer-config.yaml
network:
version: 2
ethernets:
eth0:
addresses:
- 10.0.250.3/24 # 你的静态IP
routes:
- to: 0.0.0.0/0 # （默认路由）
via: 10.0.250.1 # 你的真实网关
match:
macaddress: 3c:f6:fb:00:01:d7
set-name: eth0
nameservers:
addresses:
- 114.114.114.114
- 223.5.5.5
- 119.29.29.29
- 180.76.76.76
- 8.8.8.8
4.4 重启操作系统即可
reboot
温馨提示:
如果无法正常启动，则可用考虑将ens33网卡替换为eth0网卡，建议不要忘记写"DEVICE"字段哟。
4.5 验证加载的模块
lsmod | grep --color=auto -e ip_vs -e nf_conntrack
uname -r
ifconfig
温馨提示:
Linux kernel 4.19+版本已经将之前的"nf_conntrack_ipv4"模块更名为"nf_conntrack"模块哟~
5安装containerd+runc组件
1.安装必要的一些系统工具
apt-get -y install apt-transport-https ca-certificates curl software-properties-common
2.安装GPG证书
curl -fsSL https://mirrors.aliyun.com/docker-ce/linux/ubuntu/gpg | apt-key add -
3.写入软件源信息
add-apt-repository "deb [arch=amd64] https://mirrors.aliyun.com/docker-ce/linux/ubuntu $(lsb_release -cs) stable"
4.更新软件源
apt-get update
5.下载containerd组件
wget https://github.com/containerd/containerd/releases/download/v1.6.34/containerd-1.6.34-linux-amd64.tar.gz
安装二进制到系统路径
tar -zxvf containerd-1.6.34-linux-amd64.tar.gz --strip-components=1 -C /usr/local/bin/
建 systemd 服务文件
cat > /etc/systemd/system/containerd.service <<'EOF'
[Unit]
Description=containerd container runtime
Documentation=https://containerd.io
After=network.target local-fs.target
[Service]
ExecStartPre=-/sbin/modprobe overlay
ExecStart=/usr/local/bin/containerd
Restart=always
RestartSec=5
Delegate=yes
KillMode=process
OOMScoreAdjust=-999
LimitNOFILE=1048576
LimitNPROC=infinity
LimitCORE=infinity
[Install]
WantedBy=multi-user.target
EOF
创建命令软链接
ln -sf /usr/local/bin/ctr /usr/bin/ctr
ln -sf /usr/local/bin/containerd /usr/bin/containerd
6.配置containerd需要的模块
6.1 临时手动加载模块
modprobe -- overlay
modprobe -- br_netfilter
6.2 开机自动加载所需的内核模块
cat > /etc/modules-load.d/containerd.conf <<EOF
overlay
br_netfilter
EOF
7. 修改containerd的配置文件
6.1.重新初始化containerd的配置文件
containerd config default | tee /etc/containerd/config.toml
6.2 修改Cgroup的管理者为systemd组件
sed -ri 's#(SystemdCgroup = )false#\1true#' /etc/containerd/config.toml
grep SystemdCgroup /etc/containerd/config.toml
6.3 修改pause的基础镜像名称
sed -i 's#registry.k8s.io/pause:3.6#registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.7#' /etc/containerd/config.toml
grep sandbox_image /etc/containerd/config.toml
8.所有节点启动containerd
8.1 启动containerd服务
systemctl daemon-reload
systemctl enable --now containerd
systemctl status containerd
8.2 配置crictl客户端连接的运行时位置
cat > /etc/crictl.yaml <<EOF
runtime-endpoint: unix:///run/containerd/containerd.sock
image-endpoint: unix:///run/containerd/containerd.sock
timeout: 10
debug: false
EOF
8.3 查看containerd的版本
[root@master01 ~]# ctr version
Client:
Version: v1.6.34
Revision: e9e2c7707933f32aa891dda794a1df36a6ec7aee
Go version: go1.21.12
Server:
Version: v1.6.34
Revision: e9e2c7707933f32aa891dda794a1df36a6ec7aee
UUID: d69f7992-321b-4214-b8ac-59acba3afbd1
[root@master01 ~]# ctr plugins list | grep -i cri
io.containerd.grpc.v1 cri linux/amd64 ok
[root@master01 ~]#
- containerd的名称空间，镜像和容器，任务管理快速入门
1.名称空间管理
1.1 查看现有的名称空间
[root@master01 ~]# ctr ns ls
NAME LABELS
1.2 创建名称空间
[root@master01 ~]# ctr ns c ceshi-linux
[root@master01 ~]# ctr ns ls
NAME LABELS
test-linux
1.3 删除名称空间
[root@master01 ~]# ctr ns rm ceshi-linux
ceshi-linux
[root@master01 ~]# ctr ns ls
NAME LABELS
温馨提示:
删除的名称空间必须为空，否则无法删除！
containerd本身并不提供网络，只负责容器的生命周期。
将来网络部分交给专门的CNI插件提供。
9.1 runc部署 （全部节点）
创建存放二进制文件的目录
mkdir -p /opt/containerd/bin && mkdir -p /usr/local/bin && cd /opt/containerd/bin
wget https://github.com/opencontainers/runc/releases/download/v1.1.9/runc.amd64 -O runc
9.2 给runc添加执行权限
chmod +x /opt/containerd/bin/runc
# 软链接到系统PATH目录 /usr/bin 永久生效
ln -s /opt/containerd/bin/runc /usr/bin/runc
ln -s /opt/containerd/bin/runc /usr/local/bin/runc
验证 runc 是否安装成功
runc --version
以及ctr的使用方式
# ========== 1. 命名空间管理==========
ctr ns c linux
ctr ns ls
# ========== 2. 镜像操作 ==========
ctr -n default i pull registry.cn-hangzhou.aliyuncs.com/k8s-k8s/apps:v1
ctr -n linux i pull registry.cn-hangzhou.aliyuncs.com/k8s-k8s/apps:v2
ctr -n linux i ls
ctr -n default i rm registry.cn-hangzhou.aliyuncs.com/k8s-k8s/apps:v1
ctr -n k8s.io images import 本地镜像包.tar
ctr -n k8s.io i import 本地镜像包.tar
# ========== 3. 容器操作 ==========
ctr -n linux run registry.cn-hangzhou.aliyuncs.com/k8s-k8s/apps:v2 ceshi
ctr -n linux c ls
ctr -n linux t ls
ctr -n linux t exec -t --exec-id 2024 ceshi sh
ctr -n linux t kill ceshi
ctr -n linux c rm ceshi
ctr -n k8s.io tasks exec --exec-id $RANDOM 6f3d9a63aea69633d880f960e6a842b8eedd63074fa90a44045ebc560cd5d179 sh -c "cat /etc/nginx/conf.d/games.conf" > /root/game/games.conf
# ========== 4. 构建镜像到指定namespace（替代nerdctl build） ==========
buildctl build --frontend dockerfile.v0 --local context=. --local dockerfile=. --output type=oci,dest=ceshi-v1.tar
ctr -n linux images import ceshi-v1.tar
rm -f ceshi-v1.tar
# ========== 5. 查看容器日志（替代nerdctl logs） ==========
tail -f /run/containerd/io.containerd.runtime.v2.task/linux/ceshi/log.json
# ========== 6. 清理指定namespace无用资源（替代nerdctl prune） ==========
ctr -n linux images rm $(ctr -n linux images ls -q | grep sha256)
ctr -n linux containers rm $(ctr -n linux containers ls -q)
ctr snapshot gc
6安装etcd程序
- 安装etcd程序
1.下载etcd的软件包
[root@master01 ~]# wget https://github.com/etcd-io/etcd/releases/download/v3.5.14/etcd-v3.5.14-linux-amd64.tar.gz
2.解压etcd的二进制程序包到PATH环境变量路径
2.1 解压软件包
[root@master01 ~]# tar -xf etcd-v3.5.14-linux-amd64.tar.gz --strip-components=1 -C /usr/local/bin etcd-v3.5.14-linux-amd64/etcd{,ctl}
root@master01:~# ll /usr/local/bin/
total 169348
drwxr-xr-x 3 root root 4096 Jan 9 17:06 ./
drwxr-xr-x 10 root root 4096 May 13 2022 ../
drwxr-xr-x 2 root root 4096 Jul 18 2024 bin/
-rwxr-xr-x 1 root root 53043776 Jul 18 2024 containerd*
-rwxr-xr-x 1 root root 8032256 Jul 18 2024 containerd-shim*
-rwxr-xr-x 1 root root 10108928 Jul 18 2024 containerd-shim-runc-v1*
-rwxr-xr-x 1 root root 10141696 Jul 18 2024 containerd-shim-runc-v2*
-rwxr-xr-x 1 root root 23697472 Jul 18 2024 containerd-stress*
-rwxr-xr-x 1 root root 27663424 Jul 18 2024 ctr*
-rwxr-xr-x 1 1000 1000 23162880 May 30 2024 etcd*
-rwxr-xr-x 1 1000 1000 17543168 May 30 2024 etcdctl*
2.2 查看etcd版本
root@master01:~# etcdctl version
etcdctl version: 3.5.14
API version: 3.5
3.将软件包下发到所有节点
[root@master01 ~]# data_rsync.sh /usr/local/bin/etcd m
===== rsyncing master02: etcd =====
命令执行成功!
===== rsyncing master03: etcd =====
命令执行成功!
[root@master01 ~]#
[root@master01 ~]# data_rsync.sh /usr/local/bin/etcdctl m
===== rsyncing master02: etcdctl =====
命令执行成功!
===== rsyncing master03: etcdctl =====
命令执行成功!
8安装K8S程序
1.下载软件包
[root@master01 ~]# wget https://dl.k8s.io/v1.30.2/kubernetes-server-linux-amd64.tar.gz
2 解压K8S的二进制程序包到PATH环境变量路径
2.1 解压软件包
[root@master01 ~]# tar -xf kubernetes-server-linux-amd64.tar.gz --strip-components=3 -C /usr/local/bin kubernetes/server/bin/kube{let,ctl,-apiserver,-controller-manager,-scheduler,-proxy}
2.2 查看kubelet的版本
[root@master01 ~]# kubelet --version
Kubernetes v1.30.2
[root@master01 ~]#
3.分发软件包
[root@master01 ~]# data_rsync.sh /usr/local/bin/kube-apiserver m
[root@master01 ~]# data_rsync.sh /usr/local/bin/kube-scheduler m
[root@master01 ~]# data_rsync.sh /usr/local/bin/kube-controller-manager m
[root@master01 ~]# data_rsync.sh /usr/local/bin/kubectl m
[root@master01 ~]# data_rsync.sh /usr/local/bin/kubelet w
[root@master01 ~]# data_rsync.sh /usr/local/bin/kube-proxy w
- 生成k8s和etcd证书文件
1.安装cfssl证书管理工具
github下载地址:
https://github.com/cloudflare/cfssl
温馨提示:
生成K8S和etcd证书这一步骤很关键，我建议各位在做实验前先对K8S集群的所有节点拍一下快照，以避免你实验做失败了方便回滚。
下载软件包:
wget https://github.com/cloudflare/cfssl/releases/download/v1.6.5/cfssl-certinfo_1.6.5_linux_amd64
wget https://github.com/cloudflare/cfssl/releases/download/v1.6.5/cfssljson_1.6.5_linux_amd64
wget https://github.com/cloudflare/cfssl/releases/download/v1.6.5/cfssl_1.6.5_linux_amd64
1.2 重命名cfssl的版本号信息
[root@master01 ~]# ll cfssl*
-rw-r--r-- 1 root root 11890840 Jun 15 11:56 cfssl_1.6.5_linux_amd64
-rw-r--r-- 1 root root 8413336 Jun 15 11:56 cfssl-certinfo_1.6.5_linux_amd64
-rw-r--r-- 1 root root 6205592 Jun 15 11:56 cfssljson_1.6.5_linux_amd64
[root@master01 ~]#
[root@master01 ~]# rename -v "s/_1.6.5_linux_amd64//g" cfssl*
cfssl_1.6.5_linux_amd64 renamed as cfssl
cfssl-certinfo_1.6.5_linux_amd64 renamed as cfssl-certinfo
cfssljson_1.6.5_linux_amd64 renamed as cfssljson
[root@master01 ~]#
[root@master01 ~]# ll cfssl*
-rw-r--r-- 1 root root 11890840 Jun 15 11:56 cfssl
-rw-r--r-- 1 root root 8413336 Jun 15 11:56 cfssl-certinfo
-rw-r--r-- 1 root root 6205592 Jun 15 11:56 cfssljson
1.3 将cfssl证书拷贝到环境变量并授权执行权限
[root@master01 ~]# mv cfssl* /usr/local/bin/
[root@master01 ~]#
[root@master01 ~]# chmod +x /usr/local/bin/cfssl*
[root@master01 ~]#
[root@master01 ~]# ll /usr/local/bin/cfssl*
-rwxr-xr-x 1 root root 11890840 Jun 15 11:56 /usr/local/bin/cfssl*
-rwxr-xr-x 1 root root 8413336 Jun 15 11:56 /usr/local/bin/cfssl-certinfo*
-rwxr-xr-x 1 root root 6205592 Jun 15 11:56 /usr/local/bin/cfssljson*
- 生成etcd证书
1 master01节点创建etcd证书存储目录
[root@master01 ~]# mkdir -pv /k8s/certs/{etcd,pki}/ && cd /k8s/certs/pki/
2 master01节点生成etcd证书的自建ca证书
2.1.生成证书的CSR文件： 证书签发请求文件，配置了一些域名，公司，单位
[root@master01 pki]# cat > etcd-ca-csr.json <<EOF
{
"CN": "etcd",
"key": {
"algo": "rsa",
"size": 2048
},
"names": [
{
"C": "CN",
"ST": "Beijing",
"L": "Beijing",
"O": "etcd",
"OU": "Etcd Security"
}
],
"ca": {
"expiry": "876000h"
}
}
EOF
2.2 生成etcd CA证书和CA证书的key
root@master01:/k8s/certs/pki# cfssl gencert -initca etcd-ca-csr.json | cfssljson -bare /k8s/certs/etcd/etcd-ca
2026/01/09 17:38:39 [INFO] generating a new CA key and certificate from CSR
2026/01/09 17:38:39 [INFO] generate received request
2026/01/09 17:38:39 [INFO] received CSR
2026/01/09 17:38:39 [INFO] generating key: rsa-2048
2026/01/09 17:38:40 [INFO] encoded CSR
2026/01/09 17:38:40 [INFO] signed certificate with serial number 231888666002004471702628867331049544481049007125
[root@master01 pki]#
root@master01:/k8s/certs/pki# pwd
/k8s/certs/pki
root@master01:/k8s/certs/pki# ll /k8s/certs/etcd/
total 20
drwxr-xr-x 2 root root 4096 Jan 9 17:38 ./
drwxr-xr-x 4 root root 4096 Jan 9 17:38 ../
-rw------- 1 root root 1679 Jan 9 17:38 etcd-ca-key.pem
-rw-r--r-- 1 root root 1050 Jan 9 17:38 etcd-ca.csr
-rw-r--r-- 1 root root 1318 Jan 9 17:38 etcd-ca.pem
3 master01节点基于自建ca证书颁发etcd证书
3.1 生成etcd证书的有效期为100年
[root@master01 pki]# cat > ca-config.json <<EOF
{
"signing": {
"default": {
"expiry": "876000h"
},
"profiles": {
"kubernetes": {
"usages": [
"signing",
"key encipherment",
"server auth",
"client auth"
],
"expiry": "876000h"
}
}
}
}
EOF
3.2 生成证书的CSR文件： 证书签发请求文件，配置了一些域名，公司，单位
[root@master01 pki]# cat > etcd-csr.json <<EOF
{
"CN": "etcd",
"key": {
"algo": "rsa",
"size": 2048
},
"names": [
{
"C": "CN",
"ST": "Beijing",
"L": "Beijing",
"O": "etcd",
"OU": "Etcd Security"
}
]
}
EOF
pgsql
3.3 基于自建的ectd ca证书生成etcd的证书
[root@master01 pki]# cfssl gencert \
-ca=/k8s/certs/etcd/etcd-ca.pem \
-ca-key=/k8s/certs/etcd/etcd-ca-key.pem \
-config=ca-config.json \
--hostname=127.0.0.1,master01,master02,master03,10.0.250.3,10.0.250.4,10.0.250.5 \
--profile=kubernetes \
etcd-csr.json | cfssljson -bare /k8s/certs/etcd/etcd-server
4 k8s-master01节点将etcd证书拷贝到其他两个master节点
[root@master01 pki]# MasterNodes='master02 master03'
[root@master01 pki]#
[root@master01 pki]# for NODE in $MasterNodes; do ssh $NODE "mkdir -pv /k8s/certs/etcd/"; done
[root@master01 pki]#
[root@master01 pki]# data_rsync.sh /k8s/certs/etcd/etcd-ca-key.pem m
===== rsyncing k8s-master02: etcd-ca-key.pem =====
命令执行成功!
===== rsyncing k8s-master03: etcd-ca-key.pem =====
命令执行成功!
[root@master01 pki]# data_rsync.sh /k8s/certs/etcd/etcd-ca.pem m
===== rsyncing master02: etcd-ca.pem =====
命令执行成功!
===== rsyncing master03: etcd-ca.pem =====
命令执行成功!
[root@master01 pki]#
[root@master01 pki]# data_rsync.sh /k8s/certs/etcd/etcd-server-key.pem m
===== rsyncing master02: etcd-server-key.pem =====
命令执行成功!
===== rsyncing master03: etcd-server-key.pem =====
命令执行成功!
[root@master01 pki]#
[root@master01 pki]# data_rsync.sh /k8s/certs/etcd/etcd-server.pem m
===== rsyncing master02: etcd-server.pem =====
命令执行成功!
===== rsyncing master03: etcd-server.pem =====
命令执行成功!
9启动etcd集群
1 创建etcd集群各节点配置文件
1.1 master01节点的配置文件
[root@master01 ~]# mkdir -pv /k8s/softwares/etcd
[root@master01 ~]# cat > /k8s/softwares/etcd/etcd.config.yml <<'EOF'
name: 'master01'
data-dir: /var/lib/etcd
wal-dir: /var/lib/etcd/wal
snapshot-count: 5000
heartbeat-interval: 100
election-timeout: 1000
quota-backend-bytes: 0
listen-peer-urls: 'https://10.0.250.3:2380'
listen-client-urls: 'https://10.0.250.3:2379,http://127.0.0.1:2379'
max-snapshots: 3
max-wals: 5
cors:
initial-advertise-peer-urls: 'https://10.0.250.3:2380'
advertise-client-urls: 'https://10.0.250.3:2379'
discovery:
discovery-fallback: 'proxy'
discovery-proxy:
discovery-srv:
initial-cluster: 'master01=https://10.0.250.3:2380,master02=https://10.0.250.4:2380,master03=https://10.0.250.5:2380'
initial-cluster-token: 'etcd-k8s-cluster'
initial-cluster-state: 'new'
strict-reconfig-check: false
enable-v2: true
enable-pprof: true
proxy: 'off'
proxy-failure-wait: 5000
proxy-refresh-interval: 30000
proxy-dial-timeout: 1000
proxy-write-timeout: 5000
proxy-read-timeout: 0
client-transport-security:
cert-file: '/k8s/certs/etcd/etcd-server.pem'
key-file: '/k8s/certs/etcd/etcd-server-key.pem'
client-cert-auth: true
trusted-ca-file: '/k8s/certs/etcd/etcd-ca.pem'
auto-tls: true
peer-transport-security:
cert-file: '/k8s/certs/etcd/etcd-server.pem'
key-file: '/k8s/certs/etcd/etcd-server-key.pem'
peer-client-cert-auth: true
trusted-ca-file: '/k8s/certs/etcd/etcd-ca.pem'
auto-tls: true
debug: false
log-package-levels:
log-outputs: [default]
force-new-cluster: false
EOF
1.2 master02节点的配置文件
[root@master02 ~]# mkdir -pv /k8s/softwares/etcd
[root@master02 ~]# cat > /k8s/softwares/etcd/etcd.config.yml << 'EOF'
name: 'master02'
data-dir: /var/lib/etcd
wal-dir: /var/lib/etcd/wal
snapshot-count: 5000
heartbeat-interval: 100
election-timeout: 1000
quota-backend-bytes: 0
listen-peer-urls: 'https://10.0.250.4:2380'
listen-client-urls: 'https://10.0.250.4:2379,http://127.0.0.1:2379'
max-snapshots: 3
max-wals: 5
cors:
initial-advertise-peer-urls: 'https://10.0.250.4:2380'
advertise-client-urls: 'https://10.0.250.4:2379'
discovery:
discovery-fallback: 'proxy'
discovery-proxy:
discovery-srv:
initial-cluster: 'master01=https://10.0.250.3:2380,master02=https://10.0.250.4:2380,master03=https://10.0.250.5:2380'
initial-cluster-token: 'etcd-k8s-cluster'
initial-cluster-state: 'new'
strict-reconfig-check: false
enable-v2: true
enable-pprof: true
proxy: 'off'
proxy-failure-wait: 5000
proxy-refresh-interval: 30000
proxy-dial-timeout: 1000
proxy-write-timeout: 5000
proxy-read-timeout: 0
client-transport-security:
cert-file: '/k8s/certs/etcd/etcd-server.pem'
key-file: '/k8s/certs/etcd/etcd-server-key.pem'
client-cert-auth: true
trusted-ca-file: '/k8s/certs/etcd/etcd-ca.pem'
auto-tls: true
peer-transport-security:
cert-file: '/k8s/certs/etcd/etcd-server.pem'
key-file: '/k8s/certs/etcd/etcd-server-key.pem'
peer-client-cert-auth: true
trusted-ca-file: '/k8s/certs/etcd/etcd-ca.pem'
auto-tls: true
debug: false
log-package-levels:
log-outputs: [default]
force-new-cluster: false
EOF
1.3 master03节点的配置文件
[root@master03 ~]# mkdir -pv /k8s/softwares/etcd
[root@master03 ~]# cat > /k8s/softwares/etcd/etcd.config.yml << 'EOF'
name: 'master03'
data-dir: /var/lib/etcd
wal-dir: /var/lib/etcd/wal
snapshot-count: 5000
heartbeat-interval: 100
election-timeout: 1000
quota-backend-bytes: 0
listen-peer-urls: 'https://10.0.250.5:2380'
listen-client-urls: 'https://10.0.250.5:2379,http://127.0.0.1:2379'
max-snapshots: 3
max-wals: 5
cors:
initial-advertise-peer-urls: 'https://10.0.250.5:2380'
advertise-client-urls: 'https://10.0.250.5:2379'
discovery:
discovery-fallback: 'proxy'
discovery-proxy:
discovery-srv:
initial-cluster: 'master01=https://10.0.250.3:2380,master02=https://10.0.250.4:2380,master03=https://10.0.250.5:2380'
initial-cluster-token: 'etcd-k8s-cluster'
initial-cluster-state: 'new'
strict-reconfig-check: false
enable-v2: true
enable-pprof: true
proxy: 'off'
proxy-failure-wait: 5000
proxy-refresh-interval: 30000
proxy-dial-timeout: 1000
proxy-write-timeout: 5000
proxy-read-timeout: 0
client-transport-security:
cert-file: '/k8s/certs/etcd/etcd-server.pem'
key-file: '/k8s/certs/etcd/etcd-server-key.pem'
client-cert-auth: true
trusted-ca-file: '/k8s/certs/etcd/etcd-ca.pem'
auto-tls: true
peer-transport-security:
cert-file: '/k8s/certs/etcd/etcd-server.pem'
key-file: '/k8s/certs/etcd/etcd-server-key.pem'
peer-client-cert-auth: true
trusted-ca-file: '/k8s/certs/etcd/etcd-ca.pem'
auto-tls: true
debug: false
log-package-levels:
log-outputs: [default]
force-new-cluster: false
EOF
2 master[01-03]编写etcd启动脚本
cat > /usr/lib/systemd/system/etcd.service <<'EOF'
[Unit]
Description=Etcd Service
Documentation=https://coreos.com/etcd/docs/latest/
After=network.target
[Service]
Type=notify
ExecStart=/usr/local/bin/etcd --config-file=/k8s/softwares/etcd/etcd.config.yml
Restart=on-failure
RestartSec=10
LimitNOFILE=65536
[Install]
WantedBy=multi-user.target
Alias=etcd3.service
EOF
3.启动etcd集群
3.1.启动服务
systemctl daemon-reload && systemctl enable --now etcd
systemctl status etcd
3.2 查看etcd集群状态
etcdctl --endpoints="10.0.250.3:2379,10.0.250.4:2379,10.0.250.5:2379" --cacert=/k8s/certs/etcd/etcd-ca.pem --cert=/k8s/certs/etcd/etcd-server.pem --key=/k8s/certs/etcd/etcd-server-key.pem endpoint status --write-out=table
其他节点要查询记得检查下etcdctl是否同步
scp /usr/local/bin/etcdctl root@10.0.250.4:/usr/local/bin/
chmod +x /usr/local/bin/etcdctl
scp /usr/local/bin/etcdctl root@10.0.250.5:/usr/local/bin/
chmod +x /usr/local/bin/etcdctl
etcdctl version
3.3 验证etcd高可用
停用任意节点的ectd观察集群是否正常工作。
10生成k8s组件相关证书
1 所有节点创建k8s证书存储目录
mkdir -pv /k8s/certs/kubernetes/
2 master01节点生成kubernetes自建ca证书
2.1 生成证书的CSR文件： 证书签发请求文件，配置了一些域名，公司，单位
[root@master01 pki]# pwd
/k8s/certs/pki
[root@master01 pki]#
[root@master01 pki]# cat > k8s-ca-csr.json <<EOF
{
"CN": "kubernetes",
"key": {
"algo": "rsa",
"size": 2048
},
"names": [
{
"C": "CN",
"ST": "Beijing",
"L": "Beijing",
"O": "Kubernetes",
"OU": "Kubernetes-manual"
}
],
"ca": {
"expiry": "876000h"
}
}
EOF
2.2 生成kubernetes证书
[root@master01 pki]# cfssl gencert -initca k8s-ca-csr.json | cfssljson -bare /k8s/certs/kubernetes/k8s-ca
2026/01/09 18:10:23 [INFO] generating a new CA key and certificate from CSR
2026/01/09 18:10:23 [INFO] generate received request
2026/01/09 18:10:23 [INFO] received CSR
2026/01/09 18:10:23 [INFO] generating key: rsa-2048
2026/01/09 18:10:23 [INFO] encoded CSR
2026/01/09 18:10:23 [INFO] signed certificate with serial number 188821408404704962725530815976967191737663579456
[root@master01 pki]# ll /k8s/certs/kubernetes/
total 20
drwxr-xr-x 2 root root 4096 Jan 9 18:10 ./
drwxr-xr-x 5 root root 4096 Jan 9 18:10 ../
-rw------- 1 root root 1679 Jan 9 18:10 k8s-ca-key.pem
-rw-r--r-- 1 root root 1070 Jan 9 18:10 k8s-ca.csr
-rw-r--r-- 1 root root 1363 Jan 9 18:10 k8s-ca.pem
[root@master01 pki]#
3 k8s-master01节点基于自建ca证书颁发apiserver相关证书
3.1 生成k8s证书的有效期为100年
[root@master01 pki]# cat > k8s-ca-config.json <<EOF
{
"signing": {
"default": {
"expiry": "876000h"
},
"profiles": {
"kubernetes": {
"usages": [
"signing",
"key encipherment",
"server auth",
"client auth"
],
"expiry": "876000h"
}
}
}
}
EOF
3.2 生成apiserver证书的CSR文件： 证书签发请求文件，配置了一些域名，公司，单位
[root@master01 pki]# cat > apiserver-csr.json <<EOF
{
"CN": "kube-apiserver",
"key": {
"algo": "rsa",
"size": 2048
},
"names": [
{
"C": "CN",
"ST": "Beijing",
"L": "Beijing",
"O": "Kubernetes",
"OU": "Kubernetes-manual"
}
]
}
EOF
3.3 基于自建ca证书生成apiServer的证书文件
[root@master01 pki]# cfssl gencert \
-ca=/k8s/certs/kubernetes/k8s-ca.pem \
-ca-key=/k8s/certs/kubernetes/k8s-ca-key.pem \
-config=k8s-ca-config.json \
--hostname=10.200.0.1,10.0.250.2,kubernetes,kubernetes.default,kubernetes.default.svc,kubernetes.default.svc.k8s,kubernetes.default.svc.k8s.com,10.0.250.3,10.0.250.4,10.0.250.5,10.0.250.6,10.0.250.7 \
--profile=kubernetes \
apiserver-csr.json | cfssljson -bare /k8s/certs/kubernetes/apiserver
[root@master01 pki]# ll /k8s/certs/kubernetes/apiserver*
-rw------- 1 root root 1675 Jan 9 18:11 /k8s/certs/kubernetes/apiserver-key.pem
-rw-r--r-- 1 root root 1293 Jan 9 18:11 /k8s/certs/kubernetes/apiserver.csr
-rw-r--r-- 1 root root 1688 Jan 9 18:11 /k8s/certs/kubernetes/apiserver.pem
温馨提示:
"10.200.0.1"为咱们的svc网段的第一个地址，您需要根据自己的场景稍作修改。
"10.0.250.2"是负载均衡器的VIP地址。
"kubernetes,...,kubernetes.default.svc.k8s.com"对应的是apiServer解析的A记录。
"10.0.250.3,...,10.0.250.7"对应的是K8S集群的地址。
4 生成第三方组件与apiServer通信的聚合证书
聚合证书的作用就是让第三方组件(比如metrics-server等)能够拿这个证书文件和apiServer进行通信。
4.1 生成聚合证书的用于自建ca的CSR文件
[root@master01 pki]# cat > front-proxy-ca-csr.json <<EOF
{
"CN": "kubernetes",
"key": {
"algo": "rsa",
"size": 2048
}
}
EOF
4.2 生成聚合证书的自建ca证书
[root@master01 pki]# cfssl gencert -initca front-proxy-ca-csr.json | cfssljson -bare /k8s/certs/kubernetes/front-proxy-ca
[root@master01 pki]# ll /k8s/certs/kubernetes/front-proxy-ca*
-rw------- 1 root root 1679 Jan 9 18:12 /k8s/certs/kubernetes/front-proxy-ca-key.pem
-rw-r--r-- 1 root root 891 Jan 9 18:12 /k8s/certs/kubernetes/front-proxy-ca.csr
-rw-r--r-- 1 root root 1094 Jan 9 18:12 /k8s/certs/kubernetes/front-proxy-ca.pem
[root@master01 pki]#
4.3 生成聚合证书的用于客户端的CSR文件
[root@master01 pki]# cat > front-proxy-client-csr.json <<EOF
{
"CN": "front-proxy-client",
"key": {
"algo": "rsa",
"size": 2048
}
}
EOF
4.4 基于聚合证书的自建ca证书签发聚合证书的客户端证书
[root@master01 pki]# cfssl gencert \
-ca=/k8s/certs/kubernetes/front-proxy-ca.pem \
-ca-key=/k8s/certs/kubernetes/front-proxy-ca-key.pem \
-config=k8s-ca-config.json \
-profile=kubernetes \
front-proxy-client-csr.json | cfssljson -bare /k8s/certs/kubernetes/front-proxy-client
[root@master01 pki]# ll /k8s/certs/kubernetes/front-proxy-client*
-rw------- 1 root root 1679 Jan 9 18:13 /k8s/certs/kubernetes/front-proxy-client-key.pem
-rw-r--r-- 1 root root 903 Jan 9 18:13 /k8s/certs/kubernetes/front-proxy-client.csr
-rw-r--r-- 1 root root 1188 Jan 9 18:13 /k8s/certs/kubernetes/front-proxy-client.pem
5 生成controller-manager证书及kubeconfig文件
5.1 生成controller-manager的CSR文件
[root@master01 pki]# cat > controller-manager-csr.json <<EOF
{
"CN": "system:kube-controller-manager",
"key": {
"algo": "rsa",
"size": 2048
},
"names": [
{
"C": "CN",
"ST": "Beijing",
"L": "Beijing",
"O": "system:kube-controller-manager",
"OU": "Kubernetes-manual"
}
]
}
EOF
-------------------------------------------------C---------------------------------------------------
5.2 生成controller-manager证书文件
[root@master01 pki]# cfssl gencert \
-ca=/k8s/certs/kubernetes/k8s-ca.pem \
-ca-key=/k8s/certs/kubernetes/k8s-ca-key.pem \
-config=k8s-ca-config.json \
-profile=kubernetes \
controller-manager-csr.json | cfssljson -bare /k8s/certs/kubernetes/controller-manager
[root@master01 pki]# ll /k8s/certs/kubernetes/controller-manager*
-rw------- 1 root root 1679 Jan 9 18:14 /k8s/certs/kubernetes/controller-manager-key.pem
-rw-r--r-- 1 root root 1082 Jan 9 18:14 /k8s/certs/kubernetes/controller-manager.csr
-rw-r--r-- 1 root root 1501 Jan 9 18:14 /k8s/certs/kubernetes/controller-manager.pem
5.3.创建一个kubeconfig目录
[root@master01 pki]# mkdir -pv /k8s/certs/kubeconfig
5.4.设置一个集群
[root@master01 pki]# kubectl config set-cluster k8s-k8s \
--certificate-authority=/k8s/certs/kubernetes/k8s-ca.pem \
--embed-certs=true \
--server=https://10.0.250.2:8443 \
--kubeconfig=/k8s/certs/kubeconfig/kube-controller-manager.kubeconfig
5.5 设置一个用户项
[root@master01 pki]# kubectl config set-credentials system:kube-controller-manager \
--client-certificate=/k8s/certs/kubernetes/controller-manager.pem \
--client-key=/k8s/certs/kubernetes/controller-manager-key.pem \
--embed-certs=true \
--kubeconfig=/k8s/certs/kubeconfig/kube-controller-manager.kubeconfig
5.6 设置一个上下文环境
[root@master01 pki]# kubectl config set-context system:kube-controller-manager@kubernetes \
--cluster=k8s-k8s \
--user=system:kube-controller-manager \
--kubeconfig=/k8s/certs/kubeconfig/kube-controller-manager.kubeconfig
5.7 使用默认的上下文
[root@master01 pki]# kubectl config use-context system:kube-controller-manager@kubernetes \
--kubeconfig=/k8s/certs/kubeconfig/kube-controller-manager.kubeconfig
6 生成scheduler证书及kubeconfig文件
6.1 生成scheduler的CSR文件
[root@master01 pki]# cat > scheduler-csr.json <<EOF
{
"CN": "system:kube-scheduler",
"key": {
"algo": "rsa",
"size": 2048
},
"names": [
{
"C": "CN",
"ST": "Beijing",
"L": "Beijing",
"O": "system:kube-scheduler",
"OU": "Kubernetes-manual"
}
]
}
EOF
6.2 生成scheduler证书文件
[root@master01 pki]# cfssl gencert \
-ca=/k8s/certs/kubernetes/k8s-ca.pem \
-ca-key=/k8s/certs/kubernetes/k8s-ca-key.pem \
-config=k8s-ca-config.json \
-profile=kubernetes \
scheduler-csr.json | cfssljson -bare /k8s/certs/kubernetes/scheduler
[root@master01 pki]# ll /k8s/certs/kubernetes/scheduler*
-rw------- 1 root root 1679 Jan 9 18:19 /k8s/certs/kubernetes/scheduler-key.pem
-rw-r--r-- 1 root root 1058 Jan 9 18:19 /k8s/certs/kubernetes/scheduler.csr
-rw-r--r-- 1 root root 1476 Jan 9 18:19 /k8s/certs/kubernetes/scheduler.pem
6.3.设置一个集群
[root@master01 pki]# kubectl config set-cluster k8s-k8s \
--certificate-authority=/k8s/certs/kubernetes/k8s-ca.pem \
--embed-certs=true \
--server=https://10.0.250.2:8443 \
--kubeconfig=/k8s/certs/kubeconfig/kube-scheduler.kubeconfig
6.4 设置一个用户项
[root@master01 pki]# kubectl config set-credentials system:kube-scheduler \
--client-certificate=/k8s/certs/kubernetes/scheduler.pem \
--client-key=/k8s/certs/kubernetes/scheduler-key.pem \
--embed-certs=true \
--kubeconfig=/k8s/certs/kubeconfig/kube-scheduler.kubeconfig
6.5 设置一个上下文环境
[root@master01 pki]# kubectl config set-context system:kube-scheduler@kubernetes \
--cluster=k8s-k8s \
--user=system:kube-scheduler \
--kubeconfig=/k8s/certs/kubeconfig/kube-scheduler.kubeconfig
6.6 使用默认的上下文
[root@master01 pki]# kubectl config use-context system:kube-scheduler@kubernetes \
--kubeconfig=/k8s/certs/kubeconfig/kube-scheduler.kubeconfig
7 配置k8s集群管理员证书及kubeconfig文件
7.1 生成管理员的CSR文件
[root@master01 pki]# cat > admin-csr.json <<EOF
{
"CN": "admin",
"key": {
"algo": "rsa",
"size": 2048
},
"names": [
{
"C": "CN",
"ST": "Beijing",
"L": "Beijing",
"O": "system:masters",
"OU": "Kubernetes-manual"
}
]
}
EOF
7.2.生成k8s集群管理员证书
[root@master01 pki]# cfssl gencert \
-ca=/k8s/certs/kubernetes/k8s-ca.pem \
-ca-key=/k8s/certs/kubernetes/k8s-ca-key.pem \
-config=k8s-ca-config.json \
-profile=kubernetes \
admin-csr.json | cfssljson -bare /k8s/certs/kubernetes/admin
[root@master01 pki]# ll /k8s/certs/kubernetes/admin*
-rw------- 1 root root 1675 Jan 9 18:20 /k8s/certs/kubernetes/admin-key.pem
-rw-r--r-- 1 root root 1025 Jan 9 18:20 /k8s/certs/kubernetes/admin.csr
-rw-r--r-- 1 root root 1444 Jan 9 18:20 /k8s/certs/kubernetes/admin.pem
7.2 设置一个集群
[root@master01 pki]# kubectl config set-cluster k8s-k8s \
--certificate-authority=/k8s/certs/kubernetes/k8s-ca.pem \
--embed-certs=true \
--server=https://10.0.250.2:8443 \
--kubeconfig=/k8s/certs/kubeconfig/kube-admin.kubeconfig
7.4 设置一个用户项
[root@master01 pki]# kubectl config set-credentials kube-admin \
--client-certificate=/k8s/certs/kubernetes/admin.pem \
--client-key=/k8s/certs/kubernetes/admin-key.pem \
--embed-certs=true \
--kubeconfig=/k8s/certs/kubeconfig/kube-admin.kubeconfig
7.5 设置一个上下文环境
[root@master01 pki]# kubectl config set-context kube-admin@k8s-k8s\
--kubeconfig=/k8s/certs/kubeconfig/kube-admin.kubeconfig \
--cluster=k8s-k8s \
--user=kube-admin
7.6.使用默认的上下文
[root@master01 pki]# kubectl config use-context kube-admin@k8s-k8s\
--kubeconfig=/k8s/certs/kubeconfig/kube-admin.kubeconfig
11创建ServiceAccount
8.1.ServiceAccount是k8s一种认证方式，创建ServiceAccount的时候会创建一个与之绑定的secret，这个secret会生成一个token
[root@master01 pki]# openssl genrsa -out /k8s/certs/kubernetes/sa.key 2048
8.2.基于sa.key创建sa.pub
[root@master01 pki]# openssl rsa -in /k8s/certs/kubernetes/sa.key -pubout -out /k8s/certs/kubernetes/sa.pub
[root@master01 pki]#
[root@master01 pki]# ll /k8s/certs/kubernetes/sa*
-rw------- 1 root root 1704 Jun 24 16:11 /k8s/certs/kubernetes/sa.key
-rw-r--r-- 1 root root 451 Jun 24 16:11 /k8s/certs/kubernetes/sa.pub
9 master01节点K8S组件证书拷贝到其他两个master节点
9.1 master01节点将etcd证书拷贝到其他两个master节点
[root@master01 pki]# data_rsync.sh /k8s/certs/kubernetes m
[root@master01 pki]# data_rsync.sh /k8s/certs/kubeconfig m
9.2 其他两个节点验证文件数量是否正确【k8s-master[01-03]】
ls /k8s/certs/kubernetes | wc -l
23
ls /k8s/certs/kubeconfig | wc -l
3
- 高可用组件haproxy+keepalived安装及验证（云服务器跳过keepalived haproxy 内容用nginx lb转发）
1 所有master【k8s-master[01-03]】节点安装高可用组件
温馨提示:
- 对于高可用组件，其实我们也可以单独找两台虚拟机来部署，但我为了节省2台机器，就直接在master节点复用了。
- 如果在云上安装K8S则无安装高可用组件了，毕竟公有云大部分都是不支持keepalived的，可以直接使用云产品，比如阿里的"SLB"，腾讯的"ELB"等SAAS产品;
- 推荐使用ELB，SLB有回环的问题，也就是SLB代理的服务器不能反向访问SLB，但是腾讯云修复了这个问题;
具体实操:
apt-get -y install keepalived haproxy
2.所有master节点配置haproxy
温馨提示:
- haproxy的负载均衡器监听地址我配置是8443，你可以修改为其他端口，haproxy会用来反向代理各个master组件的地址;
- 如果你真的修改晴一定注意上面的证书配置的kubeconfig文件，也要一起修改，否则就会出现链接集群失败的问题;
具体实操:
2.1 备份配置文件
cp /etc/haproxy/haproxy.cfg{,`date +%F`}
2.2 所有节点的配置文件内容相同
cat > /etc/haproxy/haproxy.cfg <<'EOF'
global
maxconn 2000
ulimit-n 16384
log 127.0.0.1 local0 err
stats timeout 30s
defaults
log global
mode http
option httplog
option forwardfor
timeout connect 5s
timeout client 30s
timeout server 30s
timeout http-request 10s
timeout http-keep-alive 10s
frontend monitor-haproxy
bind 0.0.0.0:9999
mode http
option httplog
monitor-uri /ruok
option httplog clf
default_backend backend-nodes-9999
frontend k8s-k8s
bind 0.0.0.0:8443
mode tcp
option tcplog
tcp-request inspect-delay 5s
default_backend k8s-k8s
backend k8s-k8s
mode tcp
option tcp-check
balance roundrobin
default-server inter 10s downinter 5s rise 2 fall 2 slowstart 60s maxconn 250 maxqueue 256 weight 100
server master01 10.0.250.3:6443 check
server master02 10.0.250.4:6443 check
server master03 10.0.250.5:6443 check
backend backend-nodes-9999
mode http
option httplog
option httpchk GET /ruok
balance roundrobin
server master01 10.0.250.3:9999 check inter 2s rise 2 fall 2
server master02 10.0.250.4:9999 check inter 2s rise 2 fall 2
server master03 10.0.250.5:9999 check inter 2s rise 2 fall 2
EOF
3.所有master节点配置keepalived
温馨提示:
- 注意"interface"字段为你的物理网卡的名称，如果你的网卡是ens33，请将"eth0"修改为"ens33"哟;
- 注意"mcast_src_ip"各master节点的配置均不相同，修改根据实际环境进行修改哟;
- 注意"virtual_ipaddress"指定的是负载均衡器的VIP地址，这个地址也要和kubeconfig文件的Apiserver地址要一致哟;
- 注意"script"字段的脚本用于检测后端的apiServer是否健康;
- 注意"router_id"字段为节点ip，master每个节点配置自己的IP
具体实操:
1."master01"节点创建配置文件
[root@master01 ~]# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.0.250.3 netmask 255.255.255.0 broadcast 10.0.250.255
inet6 fe80::3ef6:fbff:fe00:1d7 prefixlen 64 scopeid 0x20<link>
ether 3c:f6:fb:00:01:d7 txqueuelen 1000 (Ethernet)
RX packets 1034658 bytes 628847159 (628.8 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 861305 bytes 487140314 (487.1 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
..
[root@master01 ~]#
cat > /etc/keepalived/keepalived.conf <<'EOF'
! Configuration File for keepalived
global_defs {
router_id 10.0.250.3
vrrp_garp_master_delay 1
vrrp_garp_master_refresh 5
}
vrrp_script chk_haproxy {
script "/etc/keepalived/check_haproxy.sh 8443"
interval 2
weight -20
fall 2
rise 2
}
vrrp_instance VI_1 {
state MASTER
interface eth0
virtual_router_id 251
priority 120
advert_int 1
nopreempt
authentication {
auth_type PASS
auth_pass k8s_k8s
}
track_script {
chk_haproxy
}
virtual_ipaddress {
10.0.250.2/32 dev eth0 scope global
}
unicast_peer {
10.0.250.4
10.0.250.5
}
notify_master "/usr/sbin/arping -U 10.0.250.2 -c 5 -I eth0"
notify_backup "/usr/sbin/arping -U 10.0.250.2 -c 5 -I eth0"
}
EOF
2."master02"节点创建配置文件
[root@master02 ~]# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.0.250.4 netmask 255.255.255.0 broadcast 10.0.250.255
inet6 fe80::3ef6:fbff:fe00:1d8 prefixlen 64 scopeid 0x20<link>
ether 3c:f6:fb:00:01:d8 txqueuelen 1000 (Ethernet)
RX packets 465623 bytes 381159590 (381.1 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 416195 bytes 53761740 (53.7 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
...
[root@master02 ~]# cat > /etc/keepalived/keepalived.conf <<EOF
! Configuration File for keepalived
global_defs {
router_id 10.0.250.4
vrrp_garp_master_delay 1
vrrp_garp_master_refresh 5
}
vrrp_script chk_haproxy {
script "/etc/keepalived/check_haproxy.sh 8443"
interval 2
weight -20
fall 2
rise 2
}
vrrp_instance VI_1 {
state BACKUP
interface eth0
virtual_router_id 251
priority 110
advert_int 1
nopreempt
authentication {
auth_type PASS
auth_pass k8s_k8s
}
track_script {
chk_haproxy
}
virtual_ipaddress {
10.0.250.2/32 dev eth0 scope global
}
unicast_peer {
10.0.250.3
10.0.250.5
}
notify_master "/usr/sbin/arping -U 10.0.250.2 -c 5 -I eth0"
notify_backup "/usr/sbin/arping -U 10.0.250.2 -c 5 -I eth0"
}
EOF
3."master03"节点创建配置文件
[root@master03 ~]# ifconfig
[root@master03 ~]# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.0.250.5 netmask 255.255.255.0 broadcast 10.0.250.255
inet6 fe80::3ef6:fbff:fe00:1d9 prefixlen 64 scopeid 0x20<link>
ether 3c:f6:fb:00:01:d9 txqueuelen 1000 (Ethernet)
RX packets 561623 bytes 258742519 (258.7 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 494933 bytes 75715526 (75.7 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
[root@master03 ~]#
[root@master03 ~]# cat > /etc/keepalived/keepalived.conf <<EOF
! Configuration File for keepalived
global_defs {
router_id 10.0.250.5
vrrp_garp_master_delay 1
vrrp_garp_master_refresh 5
}
vrrp_script chk_haproxy {
script "/etc/keepalived/check_haproxy.sh 8443"
interval 2
weight -20
fall 2
rise 2
}
vrrp_instance VI_1 {
state BACKUP
interface eth0
virtual_router_id 251
priority 100
advert_int 1
nopreempt
authentication {
auth_type PASS
auth_pass k8s_k8s
}
track_script {
chk_haproxy
}
virtual_ipaddress {
10.0.250.2/32 dev eth0 scope global
}
unicast_peer {
10.0.250.3
10.0.250.4
}
notify_master "/usr/sbin/arping -U 10.0.250.2 -c 5 -I eth0"
notify_backup "/usr/sbin/arping -U 10.0.250.2 -c 5 -I eth0"
}
EOF
4.所有keepalived节点均需要创建健康检查脚本
[root@master01 ~]# cat /etc/keepalived/check_port.sh
#!/bin/bash
CHK_PORT=$1
[ -z "$CHK_PORT" ] && { echo "Error: 检测端口不能为空！"; exit 1; }
ss -tln | grep -q ":$CHK_PORT "
if [ $? -eq 0 ]; then
exit 0
else
echo "Warning: 8443端口未监听，触发Keepalived切换..."
exit 1
fi
chmod +x /etc/keepalived/check_port.sh
5.启动keepalived服务并验证
5.1.启动keepalived服务
systemctl daemon-reload
systemctl enable --now keepalived
systemctl status keepalived
5.2 验证服务是否正常
[root@master01 ~]# ip a
1: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 3c:f6:fb:00:01:d7 brd ff:ff:ff:ff:ff:ff
altname enp0s17
altname ens17
inet 10.0.250.3/24 brd 10.0.250.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::3ef6:fbff:fe00:1d7/64 scope link
valid_lft forever preferred_lft forever
2: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000
link/ipip 0.0.0.0 brd 0.0.0.0
[root@master01 ~]# ping 10.0.250.2
...
5.3 单独开一个终端尝试停止keepalived服务
[root@master03 ~]# systemctl stop keepalived
5.4 观察终端输出
6. 验证haproxy服务并验证
6.1 所有节点启动haproxy服务
systemctl enable --now haproxy
systemctl restart haproxy
systemctl status haproxy
6.2 所有节点启动keepalived
systemctl start keepalived
systemctl start haproxy
6.3 基于telnet验证haporxy是否正常
[root@apiserver-lb ~]# telnet 10.0.250.2 8443
Trying 10.0.250.2...
Connected to 10.0.250.2.
Escape character is '^]'.
systemctl stop keepalived
systemctl stop haproxy
[root@k8s-master02 ~]#
6.4 基于webUI进行验证
[root@k8s-worker05 ~]# curl http://10.0.250.2:9999/ruok
<html><body><h1>200 OK</h1>
Service ready.
</body></html>
[root@k8s-worker05 ~]#
#查看当前飘逸位置
ip addr show eth0 | grep 10.0.250.2
（云服务器用nginx必须四层转发！）
[root@apiserver-lb ~]# cat /etc/nginx/nginx.conf
user www-data;
worker_processes auto;
pid /run/nginx.pid;
include /etc/nginx/modules-enabled/*.conf;
events {
worker_connections 1024;
}
# =============== 四层 TCP 转发 kube-apiserver ===============
stream {
# 定义后端节点
upstream k8s_master_nodes {
server 10.0.250.3:6443 max_fails=2 fail_timeout=30s;
server 10.0.250.4:6443 max_fails=2 fail_timeout=30s;
server 10.0.250.5:6443 max_fails=2 fail_timeout=30s;
}
# 监听 8443 并透传 TLS 流量
server {
listen 8443;
proxy_pass k8s_master_nodes;
# 关键参数：不终止 TLS，原样转发字节流
proxy_timeout 1h;
proxy_responses 0;
proxy_buffer_size 4k;
}
}
# ====================== http 模块保持不变 ======================
http {
sendfile on;
tcp_nopush on;
types_hash_max_size 2048;
include /etc/nginx/mime.types;
default_type application/octet-stream;
ssl_protocols TLSv1.1 TLSv1.2 TLSv1.3;
access_log /var/log/nginx/access.log;
error_log /var/log/nginx/error.log;
gzip on;
include /etc/nginx/conf.d/*.conf;
include /etc/nginx/sites-enabled/*;
}
scp /k8s/certs/kubernetes/k8s-ca.pem /k8s/certs/kubernetes/admin.pem /k8s/certs/kubernetes/admin-key.pem root@10.0.250.2:/root/
12部署ApiServer组件
- 部署ApiServer组件
1 master01节点启动ApiServer
温馨提示:
- "--advertise-address"是对应的master节点的IP地址;
- "--service-cluster-ip-range"对应的是svc的网段
- "--service-node-port-range"对应的是svc的NodePort端口范围;
- "--etcd-servers"指定的是etcd集群地址
配置文件参考链接:
https://kubernetes.io/zh-cn/docs/reference/command-line-tools-reference/kube-apiserver/
具体实操:
1.1 创建master01节点的配置文件
cat > /usr/lib/systemd/system/kube-apiserver.service << 'EOF'
[Unit]
Description=Kubernetes API Server
Documentation=https://github.com/kubernetes/kubernetes
After=network.target
[Service]
ExecStart=/usr/local/bin/kube-apiserver \
--v=2 \
--bind-address=0.0.0.0 \
--secure-port=6443 \
--allow_privileged=true \
--advertise-address=10.0.250.3 \
--service-cluster-ip-range=10.200.0.0/16 \
--service-node-port-range=3000-50000 \
--etcd-servers=https://10.0.250.3:2379,https://10.0.250.4:2379,https://10.0.250.5:2379 \
--etcd-cafile=/k8s/certs/etcd/etcd-ca.pem \
--etcd-certfile=/k8s/certs/etcd/etcd-server.pem \
--etcd-keyfile=/k8s/certs/etcd/etcd-server-key.pem \
--client-ca-file=/k8s/certs/kubernetes/k8s-ca.pem \
--tls-cert-file=/k8s/certs/kubernetes/apiserver.pem \
--tls-private-key-file=/k8s/certs/kubernetes/apiserver-key.pem \
--kubelet-client-certificate=/k8s/certs/kubernetes/apiserver.pem \
--kubelet-client-key=/k8s/certs/kubernetes/apiserver-key.pem \
--service-account-key-file=/k8s/certs/kubernetes/sa.pub \
--service-account-signing-key-file=/k8s/certs/kubernetes/sa.key \
--service-account-issuer=https://kubernetes.default.svc.oldboyedu.com \
--kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname \
--enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,NodeRestriction,ResourceQuota \
--authorization-mode=Node,RBAC \
--enable-bootstrap-token-auth=true \
--requestheader-client-ca-file=/k8s/certs/kubernetes/front-proxy-ca.pem \
--proxy-client-cert-file=/k8s/certs/kubernetes/front-proxy-client.pem \
--proxy-client-key-file=/k8s/certs/kubernetes/front-proxy-client-key.pem \
--requestheader-allowed-names=aggregator \
--requestheader-group-headers=X-Remote-Group \
--requestheader-extra-headers-prefix=X-Remote-Extra- \
--requestheader-username-headers=X-Remote-User
Restart=on-failure
RestartSec=10s
LimitNOFILE=65535
[Install]
WantedBy=multi-user.target
EOF
1.2启动服务
systemctl daemon-reload && systemctl enable --now kube-apiserver
systemctl status kube-apiserver
ss -ntl | grep 6443
2 master02节点启动ApiServer
温馨提示:
- "--advertise-address"是对应的master节点的IP地址;
- "--service-cluster-ip-range"对应的是svc的网段
- "--service-node-port-range"对应的是svc的NodePort端口范围;
- "--etcd-servers"指定的是etcd集群地址
具体实操:
2.1 创建master02节点的配置文件
cat > /usr/lib/systemd/system/kube-apiserver.service << 'EOF'
[Unit]
Description=Kubernetes API Server
Documentation=https://github.com/kubernetes/kubernetes
After=network.target
[Service]
ExecStart=/usr/local/bin/kube-apiserver \
--v=2 \
--bind-address=0.0.0.0 \
--secure-port=6443 \
--advertise-address=10.0.250.4 \
--service-cluster-ip-range=10.200.0.0/16 \
--service-node-port-range=3000-50000 \
--etcd-servers=https://10.0.250.3:2379,https://10.0.250.4:2379,https://10.0.250.5:2379 \
--etcd-cafile=/k8s/certs/etcd/etcd-ca.pem \
--etcd-certfile=/k8s/certs/etcd/etcd-server.pem \
--etcd-keyfile=/k8s/certs/etcd/etcd-server-key.pem \
--client-ca-file=/k8s/certs/kubernetes/k8s-ca.pem \
--tls-cert-file=/k8s/certs/kubernetes/apiserver.pem \
--tls-private-key-file=/k8s/certs/kubernetes/apiserver-key.pem \
--kubelet-client-certificate=/k8s/certs/kubernetes/apiserver.pem \
--kubelet-client-key=/k8s/certs/kubernetes/apiserver-key.pem \
--service-account-key-file=/k8s/certs/kubernetes/sa.pub \
--service-account-signing-key-file=/k8s/certs/kubernetes/sa.key \
--service-account-issuer=https://kubernetes.default.svc.oldboyedu.com \
--kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname \
--enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,NodeRestriction,ResourceQuota \
--authorization-mode=Node,RBAC \
--enable-bootstrap-token-auth=true \
--requestheader-client-ca-file=/k8s/certs/kubernetes/front-proxy-ca.pem \
--proxy-client-cert-file=/k8s/certs/kubernetes/front-proxy-client.pem \
--proxy-client-key-file=/k8s/certs/kubernetes/front-proxy-client-key.pem \
--requestheader-allowed-names=aggregator \
--requestheader-group-headers=X-Remote-Group \
--requestheader-extra-headers-prefix=X-Remote-Extra- \
--requestheader-username-headers=X-Remote-User
Restart=on-failure
RestartSec=10s
LimitNOFILE=65535
[Install]
WantedBy=multi-user.target
EOF
2.2 启动服务
systemctl daemon-reload && systemctl enable --now kube-apiserver
systemctl status kube-apiserver
ss -ntl | grep 6443
3 master03节点启动ApiServer
温馨提示:
- "--advertise-address"是对应的master节点的IP地址;
- "--service-cluster-ip-range"对应的是svc的网段
- "--service-node-port-range"对应的是svc的NodePort端口范围;
- "--etcd-servers"指定的是etcd集群地址
具体实操:
3.1 创建master03节点的配置文件
cat > /usr/lib/systemd/system/kube-apiserver.service << 'EOF'
[Unit]
Description=Kubernetes API Server
Documentation=https://github.com/kubernetes/kubernetes
After=network.target
[Service]
ExecStart=/usr/local/bin/kube-apiserver \
--v=2 \
--bind-address=0.0.0.0 \
--secure-port=6443 \
--advertise-address=10.0.250.5 \
--service-cluster-ip-range=10.200.0.0/16 \
--service-node-port-range=3000-50000 \
--etcd-servers=https://10.0.250.3:2379,https://10.0.250.4:2379,https://10.0.250.5:2379 \
--etcd-cafile=/k8s/certs/etcd/etcd-ca.pem \
--etcd-certfile=/k8s/certs/etcd/etcd-server.pem \
--etcd-keyfile=/k8s/certs/etcd/etcd-server-key.pem \
--client-ca-file=/k8s/certs/kubernetes/k8s-ca.pem \
--tls-cert-file=/k8s/certs/kubernetes/apiserver.pem \
--tls-private-key-file=/k8s/certs/kubernetes/apiserver-key.pem \
--kubelet-client-certificate=/k8s/certs/kubernetes/apiserver.pem \
--kubelet-client-key=/k8s/certs/kubernetes/apiserver-key.pem \
--service-account-key-file=/k8s/certs/kubernetes/sa.pub \
--service-account-signing-key-file=/k8s/certs/kubernetes/sa.key \
--service-account-issuer=https://kubernetes.default.svc.oldboyedu.com \
--kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname \
--enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,NodeRestriction,ResourceQuota \
--authorization-mode=Node,RBAC \
--enable-bootstrap-token-auth=true \
--requestheader-client-ca-file=/k8s/certs/kubernetes/front-proxy-ca.pem \
--proxy-client-cert-file=/k8s/certs/kubernetes/front-proxy-client.pem \
--proxy-client-key-file=/k8s/certs/kubernetes/front-proxy-client-key.pem \
--requestheader-allowed-names=aggregator \
--requestheader-group-headers=X-Remote-Group \
--requestheader-extra-headers-prefix=X-Remote-Extra- \
--requestheader-username-headers=X-Remote-User
Restart=on-failure
RestartSec=10s
LimitNOFILE=65535
[Install]
WantedBy=multi-user.target
EOF
3.2 启动服务
systemctl daemon-reload && systemctl enable --now kube-apiserver
systemctl status kube-apiserver
ss -ntl | grep 6443
13部署ControlerManager组件
1 所有master节点创建配置文件
温馨提示:
- "--cluster-cidr"是Pod的网段地址，我们可以自行修改。
配置文件参考链接:
https://kubernetes.io/zh-cn/docs/reference/command-line-tools-reference/kube-controller-manager/
所有节点的controller-manager组件配置文件相同: (证书文件存放的位置也要相同)
cat > /usr/lib/systemd/system/kube-controller-manager.service << 'EOF'
[Unit]
Description=Kubernetes Controller Manager
Documentation=https://github.com/kubernetes/kubernetes
After=network.target
[Service]
ExecStart=/usr/local/bin/kube-controller-manager \
--v=2 \
--root-ca-file=/k8s/certs/kubernetes/k8s-ca.pem \
--cluster-signing-cert-file=/k8s/certs/kubernetes/k8s-ca.pem \
--cluster-signing-key-file=/k8s/certs/kubernetes/k8s-ca-key.pem \
--service-account-private-key-file=/k8s/certs/kubernetes/sa.key \
--kubeconfig=/k8s/certs/kubeconfig/kube-controller-manager.kubeconfig \
--leader-elect=true \
--use-service-account-credentials=true \
--node-monitor-grace-period=40s \
--node-monitor-period=5s \
--controllers=*,bootstrapsigner,tokencleaner \
--allocate-node-cidrs=true \
--cluster-cidr=10.100.0.0/16 \
--requestheader-client-ca-file=/k8s/certs/kubernetes/front-proxy-ca.pem \
--node-cidr-mask-size=24
Restart=always
RestartSec=10s
[Install]
WantedBy=multi-user.target
EOF
2.启动controller-manager服务
systemctl daemon-reload
systemctl enable --now kube-controller-manager
systemctl status kube-controller-manager
ss -ntl | grep 10257
14部署Scheduler组件
1 所有master节点创建配置文件
配置文件参考链接:
https://kubernetes.io/zh-cn/docs/reference/command-line-tools-reference/kube-scheduler/
所有节点的controller-manager组件配置文件相同: (前提是证书文件存放的位置也要相同哟!)
cat > /usr/lib/systemd/system/kube-scheduler.service <<'EOF'
[Unit]
Description=Kubernetes Scheduler
Documentation=https://github.com/kubernetes/kubernetes
After=network.target
[Service]
ExecStart=/usr/local/bin/kube-scheduler \
--v=2 \
--leader-elect=true \
--kubeconfig=/k8s/certs/kubeconfig/kube-scheduler.kubeconfig
Restart=always
RestartSec=10s
[Install]
WantedBy=multi-user.target
EOF
2 启动scheduler服务
systemctl daemon-reload
systemctl enable --now kube-scheduler
systemctl status kube-scheduler
ss -ntl | grep 10259
15创建Bootstrapping自动颁发kubelet证书配置
1 master01节点创建bootstrap-kubelet.kubeconfig文件
温馨提示:
- "--server"只想的是负载均衡器的IP地址，由负载均衡器对master节点进行反向代理哟。
- "--token"也可以自定义，但也要同时修改"bootstrap"的Secret的"token-id"和"token-secret"对应值哟;
[root@master01 ~]# TOKEN_ID=$(openssl rand -hex 3)
[root@master01 ~]# echo $TOKEN_ID
762875
[root@master01 ~]# TOKEN_SECRET=$(openssl rand -hex 8)
[root@master01 ~]# echo $TOKEN_SECRET
3c0935dd8f229529
1.1 设置集群
kubectl config set-cluster k8s-k8s \
--certificate-authority=/k8s/certs/kubernetes/k8s-ca.pem \
--embed-certs=true \
--server=https://10.0.250.2:8443 \
--kubeconfig=/k8s/certs/kubeconfig/bootstrap-kubelet.kubeconfig
1.2 创建用户
kubectl config set-credentials tls-bootstrap-token-user \
--token=762875.3c0935dd8f229529 \
--kubeconfig=/k8s/certs/kubeconfig/bootstrap-kubelet.kubeconfig
1.3 将集群和用户进行绑定
kubectl config set-context tls-bootstrap-token-user@k8s-k8s\
--cluster=k8s-k8s \
--user=tls-bootstrap-token-user \
--kubeconfig=/k8s/certs/kubeconfig/bootstrap-kubelet.kubeconfig
1.4 配置默认的上下文
kubectl config use-context tls-bootstrap-token-user@k8s-k8s --kubeconfig=/k8s/certs/kubeconfig/bootstrap-kubelet.kubeconfig
2 所有master节点拷贝管理证书
下面的操作我以master01为案例来操作的，实际上你可以使用所有的master节点完成下面的操作
2.1 所有master都拷贝管理员的证书文件
[root@master01 ~]# mkdir -p /root/.kube
[root@master01 ~]# cp /k8s/certs/kubeconfig/kube-admin.kubeconfig /root/.kube/config
2.2 查看master组件，该组件官方在1.19+版本开始弃用，但是在1.28依旧没有移除哟~
[root@master01 ~]# kubectl get cs
Warning: v1 ComponentStatus is deprecated in v1.19+
NAME STATUS MESSAGE ERROR
scheduler Healthy ok
controller-manager Healthy ok
etcd-0 Healthy ok
2.3 查看集群状态，如果未来cs组件移除了也没关系，我们可以使用"cluster-info"子命令查看集群状态
[root@master01 ~]# kubectl cluster-info
Kubernetes control plane is running at https://10.0.250.2:8443
To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
--------------------=============-------------------如果你配置失败再次配置一定要记得删除-----------------------=-=-=-=
1. 删除无效的kubelet.kubeconfig，让kubelet优先加载修复后的bootstrap文件
rm -rf /k8s/certs/kubeconfig/kubelet.kubeconfig 2>/dev/null
rm -rf /var/lib/kubelet/pki/* 2>/dev/null
2. 重启组件，加载新配置（按顺序执行，无风险）
c
systemctl daemon-reload && systemctl restart kubelet
systemctl restart kube-apiserver kube-controller-manager kube-scheduler
master02 03
systemctl daemon-reload && systemctl restart kubelet
--------------------=============-------------------end-----------------------=-=-=-=
3 创建bootstrap-secret授权
3.1 创建配bootstrap-secret文件用于授权
cat > bootstrap-secret.yaml <<'EOF'
apiVersion: v1
kind: Secret
metadata:
name: bootstrap-token-762875
namespace: kube-system
type: bootstrap.kubernetes.io/token
stringData:
description: "Bootstrap token for kubelet TLS bootstrapping"
token-id: "762875"
token-secret: "3c0935dd8f229529"
usage-bootstrap-authentication: "true"
usage-bootstrap-signing: "true"
auth-extra-groups: "system:bootstrappers:default-node-token,system:bootstrappers:worker,system:bootstrappers:ingress"
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: kubelet-bootstrap
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: system:node-bootstrapper
subjects:
- apiGroup: rbac.authorization.k8s.io
kind: Group
name: system:bootstrappers:default-node-token
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: node-autoapprove-bootstrap
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: system:certificates.k8s.io:certificatesigningrequests:nodeclient
subjects:
- apiGroup: rbac.authorization.k8s.io
kind: Group
name: system:bootstrappers:default-node-token
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: node-autoapprove-certificate-rotation
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: system:certificates.k8s.io:certificatesigningrequests:selfnodeclient
subjects:
- apiGroup: rbac.authorization.k8s.io
kind: Group
name: system:nodes
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
annotations:
rbac.authorization.kubernetes.io/autoupdate: "true"
labels:
kubernetes.io/bootstrapping: rbac-defaults
name: system:kube-apiserver-to-kubelet
rules:
- apiGroups: [""]
resources:
- nodes/proxy
- nodes/stats
- nodes/log
- nodes/spec
- nodes/metrics
verbs: ["*"]
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: system:kube-apiserver
namespace: ""
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: system:kube-apiserver-to-kubelet
subjects:
- apiGroup: rbac.authorization.k8s.io
kind: User
name: kube-apiserver
EOF
2.应用bootstrap-secret配置文件
[root@master01 ~]# kubectl apply -f bootstrap-secret.yaml
secret/bootstrap-token-yindao created
clusterrolebinding.rbac.authorization.k8s.io/kubelet-bootstrap created
clusterrolebinding.rbac.authorization.k8s.io/node-autoapprove-bootstrap created
clusterrolebinding.rbac.authorization.k8s.io/node-autoapprove-certificate-rotation created
clusterrole.rbac.authorization.k8s.io/system:kube-apiserver-to-kubelet created
clusterrolebinding.rbac.authorization.k8s.io/system:kube-apiserver created
16部署worker+kubelet启动
1 复制证书
1.1 master01节点分发证书到其他节点
cd /k8s/certs/
for NODE in master02 master03 worker01 worker02; do
echo $NODE
ssh $NODE "mkdir -p /k8s/certs/kube{config,rnetes}"
for FILE in k8s-ca.pem k8s-ca-key.pem front-proxy-ca.pem; do
scp kubernetes/$FILE $NODE:/k8s/certs/kubernetes/${FILE}
done
scp kubeconfig/bootstrap-kubelet.kubeconfig $NODE:/k8s/certs/kubeconfig/
done
1.2 worker节点进行验证
[root@worker01 ~]# ll /k8s/ -R
/k8s/:
total 12
drwxr-xr-x 3 root root 4096 Jan 4 18:57 ./
drwxr-xr-x 20 root root 4096 Jan 4 18:57 ../
drwxr-xr-x 4 root root 4096 Jan 8 22:29 certs/
/k8s/certs:
total 16
drwxr-xr-x 4 root root 4096 Jan 8 22:29 ./
drwxr-xr-x 3 root root 4096 Jan 4 18:57 ../
drwxr-xr-x 2 root root 4096 Jan 8 22:29 kubeconfig/
drwxr-xr-x 2 root root 4096 Jan 8 22:29 kubernetes/
/k8s/certs/kubeconfig:
total 12
drwxr-xr-x 2 root root 4096 Jan 8 22:29 ./
drwxr-xr-x 4 root root 4096 Jan 8 22:29 ../
-rw------- 1 root root 2212 Jan 8 22:29 bootstrap-kubelet.kubeconfig
/k8s/certs/kubernetes:
total 20
drwxr-xr-x 2 root root 4096 Jan 8 22:29 ./
drwxr-xr-x 4 root root 4096 Jan 8 22:29 ../
-rw-r--r-- 1 root root 1094 Jan 8 22:29 front-proxy-ca.pem
-rw------- 1 root root 1675 Jan 8 22:29 k8s-ca-key.pem
-rw-r--r-- 1 root root 1363 Jan 8 22:29 k8s-ca.pem
/k8s/certs/kubernetes:
total 12
-rw-r--r-- 1 root root 1094 Nov 5 16:27 front-proxy-ca.pem
-rw------- 1 root root 1675 Nov 5 16:27 k8s-ca-key.pem
-rw-r--r-- 1 root root 1363 Nov 5 16:27 k8s-ca.pem
2 启动kubelet服务
温馨提示:
- 在"10-kubelet.con"文件中使用"--kubeconfig"指定的"kubelet.kubeconfig"文件并不存在，这个证书文件后期会自动生成;
- 对于"clusterDNS"是NDS地址，我们可以自定义，比如"10.200.0.254";
- “clusterDomain”对应的是域名信息，要和我们设计的集群保持一致，比如"k8s.com";
- "10-kubelet.conf"文件中的"ExecStart="需要写2次，否则可能无法启动kubelet;
具体实操:
2.1 所有节点创建工作目录
mkdir -p /var/lib/kubelet /var/log/kubernetes /etc/systemd/system/kubelet.service.d /etc/kubernetes/manifests/
2.2 所有节点创建kubelet的配置文件
cat > /etc/kubernetes/kubelet-conf.yml <<'EOF'
apiVersion: kubelet.config.k8s.io/v1beta1
kind: KubeletConfiguration
address: 0.0.0.0
port: 10250
readOnlyPort: 10255
authentication:
anonymous:
enabled: false
webhook:
cacheTTL: 2m0s
enabled: true
x509:
clientCAFile: /k8s/certs/kubernetes/k8s-ca.pem
authorization:
mode: Webhook
webhook:
cacheAuthorizedTTL: 5m0s
cacheUnauthorizedTTL: 30s
cgroupDriver: systemd
cgroupsPerQOS: true
clusterDNS:
- 10.200.0.254
clusterDomain: k8s.com
containerLogMaxFiles: 5
containerLogMaxSize: 10Mi
contentType: application/vnd.kubernetes.protobuf
cpuCFSQuota: true
cpuManagerPolicy: none
cpuManagerReconcilePeriod: 10s
enableControllerAttachDetach: true
enableDebuggingHandlers: true
enforceNodeAllocatable:
- pods
eventBurst: 10
eventRecordQPS: 5
evictionHard:
imagefs.available: 15%
memory.available: 100Mi
nodefs.available: 10%
nodefs.inodesFree: 5%
evictionPressureTransitionPeriod: 5m0s
failSwapOn: true
fileCheckFrequency: 20s
hairpinMode: promiscuous-bridge
healthzBindAddress: 127.0.0.1
healthzPort: 10248
httpCheckFrequency: 20s
imageGCHighThresholdPercent: 85
imageGCLowThresholdPercent: 80
imageMinimumGCAge: 2m0s
iptablesDropBit: 15
iptablesMasqueradeBit: 14
kubeAPIBurst: 10
kubeAPIQPS: 5
makeIPTablesUtilChains: true
maxOpenFiles: 1000000
maxPods: 110
nodeStatusUpdateFrequency: 10s
oomScoreAdj: -999
podPidsLimit: -1
registryBurst: 10
registryPullQPS: 5
resolvConf: /etc/resolv.conf
rotateCertificates: true
runtimeRequestTimeout: 2m0s
serializeImagePulls: true
staticPodPath: /etc/kubernetes/manifests
streamingConnectionIdleTimeout: 4h0m0s
syncFrequency: 1m0s
volumeStatsAggPeriod: 1m0s
tlsCertFile: /var/lib/kubelet/pki/kubelet.crt
tlsPrivateKeyFile: /var/lib/kubelet/pki/kubelet.key
EOF
2.3 所有节点配置kubelet service
cat > /usr/lib/systemd/system/kubelet.service <<'EOF'
[Unit]
Description=Kubernetes Kubelet
Documentation=https://github.com/kubernetes/kubernetes
After=containerd.service
Requires=containerd.service
[Service]
ExecStart=/usr/local/bin/kubelet
Restart=always
StartLimitInterval=0
RestartSec=10
[Install]
WantedBy=multi-user.target
EOF
2.4 所有节点配置kubelet service的配置文件
cat > /etc/systemd/system/kubelet.service.d/10-kubelet.conf <<'EOF'
[Service]
Environment="KUBELET_KUBECONFIG_ARGS=--bootstrap-kubeconfig=/k8s/certs/kubeconfig/bootstrap-kubelet.kubeconfig --kubeconfig=/k8s/certs/kubeconfig/kubelet.kubeconfig"
Environment="KUBELET_CONFIG_ARGS=--config=/etc/kubernetes/kubelet-conf.yml"
Environment="KUBELET_SYSTEM_ARGS=--container-runtime-endpoint=unix:///run/containerd/containerd.sock"
Environment="KUBELET_EXTRA_ARGS=--node-labels=node.kubernetes.io/node='' "
ExecStart=
ExecStart=/usr/local/bin/kubelet $KUBELET_KUBECONFIG_ARGS $KUBELET_CONFIG_ARGS $KUBELET_SYSTEM_ARGS $KUBELET_EXTRA_ARGS
EOF
2.5 启动所有节点kubelet
systemctl daemon-reload
systemctl enable --now kubelet
systemctl status kubelet
systemctl stop kubelet && systemctl daemon-reload && systemctl enable --now kubelet && systemctl status kubelet
systemctl stop kubelet
[root@master01 ~]#
scp /root/.kube/config root@master02:/root/.kube/config
scp /root/.kube/config root@master03:/root/.kube/config
2.6 在所有master节点上查看nodes信息。
[root@master01]# kubectl get nodes
NAME STATUS ROLES AGE VERSION
master01 NotReady <none> 34m v1.30.2
master02 NotReady <none> 13m v1.30.2
master03 NotReady <none> 13m v1.30.2
worker01 NotReady <none> 58s v1.30.2
worker02 NotReady <none> 58s v1.30.2
2.7 可以查看到有相应的csr用户客户端的证书请求
[root@master01]# kubectl get csr
NAME AGE SIGNERNAME REQUESTOR REQUESTEDDURATION CONDITION
csr-27ggd 3m8s kubernetes.io/kubelet-serving system:node:master02 <none> Pending
csr-8l7nm 15m kubernetes.io/kube-apiserver-client-kubelet system:bootstrap:762875 <none> Approved,Issued
csr-b5zg6 10m kubernetes.io/kubelet-serving system:node:master03 <none> Pending
csr-bbljd 15m kubernetes.io/kube-apiserver-client-kubelet system:bootstrap:762875 <none> Approved,Issued
csr-c958n 10m kubernetes.io/kubelet-serving system:node:master02 <none> Pending
csr-d5fb5 3m8s kubernetes.io/kubelet-serving system:node:master03 <none> Pending
csr-f96cg 10m kubernetes.io/kube-apiserver-client-kubelet system:bootstrap:762875 <none> Approved,Issued
csr-fg4j9 3m9s kubernetes.io/kube-apiserver-client-kubelet system:bootstrap:762875 <none> Approved,Issued
csr-l985z 15m kubernetes.io/kubelet-serving system:node:master02 <none> Pending
csr-lt25c 15m kubernetes.io/kubelet-serving system:node:master03 <none> Pending
csr-nf2kl 3m8s kubernetes.io/kubelet-serving system:node:worker01 <none> Pending
csr-tmd9p 36m kubernetes.io/kube-apiserver-client-kubelet system:bootstrap:762875 <none> Approved,Issued
csr-vrqwk 3m8s kubernetes.io/kubelet-serving system:node:worker02 <none> Pending
csr-vxfzz 9m45s kubernetes.io/kubelet-serving system:node:master03 <none> Pending
csr-w9spr 10m kubernetes.io/kube-apiserver-client-kubelet system:bootstrap:762875 <none> Approved,Issued
csr-xz6cq 10m kubernetes.io/kube-apiserver-client-kubelet system:bootstrap:762875 <none> Approved,Issued
csr-znwt9 3m9s kubernetes.io/kube-apiserver-client-kubelet system:bootstrap:762875 <none> Approved,Issued
17部署worker节点之kube-proxy服务
1.生成kube-proxy的csr文件
[root@master01 pki]# pwd
/k8s/certs/pki
[root@master01 pki]# cat > kube-proxy-csr.json <<EOF
{
"CN": "system:kube-proxy",
"key": {
"algo": "rsa",
"size": 2048
},
"names": [
{
"C": "CN",
"ST": "Beijing",
"L": "Beijing",
"O": "system:kube-proxy",
"OU": "Kubernetes-manual"
}
]
}
EOF
[root@master01 pki]# find / -name "k8s-ca-config.json"
/k8s/certs/pki/k8s-ca-config.json
[root@master01 certs]# find / -name "kube-proxy-csr.json"
/k8s/certs/kube-proxy-csr.json
cfssl gencert \
-ca=/k8s/certs/kubernetes/k8s-ca.pem \
-ca-key=/k8s/certs/kubernetes/k8s-ca-key.pem \
-config=/k8s/certs/pki/k8s-ca-config.json \
-profile=kubernetes \
/k8s/certs/kube-proxy-csr.json \
| cfssljson -bare /k8s/certs/kubernetes/kube-proxy
[root@master01 pki]# ll /k8s/certs/kubernetes/kube-proxy*
-rw------- 1 root root 1679 Jan 9 19:56 /k8s/certs/kubernetes/kube-proxy-key.pem
-rw-r--r-- 1 root root 1045 Jan 9 19:56 /k8s/certs/kubernetes/kube-proxy.csr
-rw-r--r-- 1 root root 1464 Jan 9 19:56 /k8s/certs/kubernetes/kube-proxy.pem
3.设置集群
[root@master01 pki]# kubectl config set-cluster k8s-k8s \
--certificate-authority=/k8s/certs/kubernetes/k8s-ca.pem \
--embed-certs=true \
--server=https://10.0.250.2:8443 \
--kubeconfig=/k8s/certs/kubeconfig/kube-proxy.kubeconfig
4.设置一个用户项
[root@master01 pki]# kubectl config set-credentials system:kube-proxy \
--client-certificate=/k8s/certs/kubernetes/kube-proxy.pem \
--client-key=/k8s/certs/kubernetes/kube-proxy-key.pem \
--embed-certs=true \
--kubeconfig=/k8s/certs/kubeconfig/kube-proxy.kubeconfig
5.设置一个上下文环境
[root@master01 pki]# kubectl config set-context kube-proxy@k8s-k8s \
--cluster=k8s-k8s \
--user=system:kube-proxy \
--kubeconfig=/k8s/certs/kubeconfig/kube-proxy.kubeconfig
6.使用默认的上下文
[root@master01 pki]# kubectl config use-context kube-proxy@k8s-k8s \
--kubeconfig=/k8s/certs/kubeconfig/kube-proxy.kubeconfig
检查
[root@master01 pki]# kubectl config view --kubeconfig=/k8s/certs/kubeconfig/kube-proxy.kubeconfig
apiVersion: v1
clusters:
- cluster:
certificate-authority-data: DATA+OMITTED
server: https://10.0.250.2:8443
name: k8s-k8s
contexts:
- context:
cluster: k8s-k8s
user: system:kube-proxy
name: kube-proxy@k8s-k8s
current-context: kube-proxy@k8s-k8s
kind: Config
preferences: {}
users:
- name: system:kube-proxy
user:
client-certificate-data: DATA+OMITTED
client-key-data: DATA+OMITTED
7.将kube-proxy的systemd Service文件发送到其他节点
for NODE in master02 master03 worker01 worker02; do
echo $NODE
scp /k8s/certs/kubeconfig/kube-proxy.kubeconfig $NODE:/k8s/certs/kubeconfig/
done
8.所有节点创建kube-proxy.conf配置文件，
cat > /etc/kubernetes/kube-proxy.yml << EOF
apiVersion: kubeproxy.config.k8s.io/v1alpha1
kind: KubeProxyConfiguration
bindAddress: 0.0.0.0
metricsBindAddress: 127.0.0.1:10249
clientConnection:
acceptConnection: ""
burst: 10
contentType: application/vnd.kubernetes.protobuf
kubeconfig: /k8s/certs/kubeconfig/kube-proxy.kubeconfig
qps: 5
clusterCIDR: 10.100.0.0/16
configSyncPeriod: 15m0s
conntrack:
max: null
maxPerCore: 32768
min: 131072
tcpCloseWaitTimeout: 1h0m0s
tcpEstablishedTimeout: 24h0m0s
enableProfiling: false
healthzBindAddress: 0.0.0.0:10256
hostnameOverride: ""
iptables:
masqueradeAll: false
masqueradeBit: 14
minSyncPeriod: 0s
ipvs:
masqueradeAll: true
minSyncPeriod: 5s
scheduler: "rr"
syncPeriod: 30s
mode: "ipvs"
nodeProtAddress: null
oomScoreAdj: -999
portRange: ""
udpIdelTimeout: 250ms
EOF
9.所有节点使用systemd管理kube-proxy
cat > /usr/lib/systemd/system/kube-proxy.service << EOF
[Unit]
Description=Kubernetes Proxy
After=network.target
[Service]
ExecStart=/usr/local/bin/kube-proxy \
--config=/etc/kubernetes/kube-proxy.yml \
--v=2
Restart=on-failure
LimitNOFILE=65536
[Install]
WantedBy=multi-user.target
EOF
10.所有节点启动kube-proxy
systemctl daemon-reload && systemctl enable --now kube-proxy
systemctl status kube-proxy
ss -ntl |grep 10249
18网络插件calico部署案例
参考链接:
https://docs.tigera.io/calico/latest/getting-started/kubernetes/quickstart
1.下载资源清单
[root@master02 ~]# wget https://raw.githubusercontent.com/projectcalico/calico/v3.28.0/manifests/tigera-operator.yaml
[root@master02 ~]# wget https://raw.githubusercontent.com/projectcalico/calico/v3.28.0/manifests/custom-resources.yaml
2.根据自己的K8S情况修改Pod网段
[root@master02 ~]# grep cidr custom-resources.yaml
cidr: 192.168.0.0/16
[root@master02 ~]# sed -i '/cidr/s#192.168#10.100#' custom-resources.yaml
[root@master02 ~]# grep cidr custom-resources.yaml
cidr: 10.100.0.0/16
3.部署calico
[root@master02 ~]# kubectl create -f tigera-operator.yaml
[root@master02 ~]# kubectl create -f custom-resources.yaml
4.查看calico是否部署成功
[root@master02 bin]# kubectl get pods -A -o wide
NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
calico-apiserver calico-apiserver-cb6d8fcf7-g5jlf 1/1 Running 0 3m43s 10.100.30.66 worker02 <none> <none>
calico-apiserver calico-apiserver-cb6d8fcf7-rf7g9 1/1 Running 0 3m43s 10.100.5.2 worker01 <none> <none>
calico-system calico-kube-controllers-5898bc7f6c-cv482 1/1 Running 0 12m 10.100.241.65 master01 <none> <none>
calico-system calico-node-6s22j 1/1 Running 0 12m 10.0.250.5 master03 <none> <none>
calico-system calico-node-drg5z 1/1 Running 0 12m 10.0.250.3 master01 <none> <none>
calico-system calico-node-l8ng4 1/1 Running 0 12m 10.0.250.7 worker02 <none> <none>
calico-system calico-node-qb27l 1/1 Running 0 12m 10.0.250.4 master02 <none> <none>
calico-system calico-node-wpd8f 1/1 Running 0 12m 10.0.250.6 worker01 <none> <none>
calico-system calico-typha-75cb68dc98-6bw95 1/1 Running 0 12m 10.0.250.4 master02 <none> <none>
calico-system calico-typha-75cb68dc98-gwmtt 1/1 Running 0 12m 10.0.250.7 worker02 <none> <none>
calico-system calico-typha-75cb68dc98-hj55h 1/1 Running 0 12m 10.0.250.6 worker01 <none> <none>
calico-system csi-node-driver-98kt9 2/2 Running 0 12m 10.100.5.1 worker01 <none> <none>
calico-system csi-node-driver-ghvpw 2/2 Running 1 (2m19s ago) 12m 10.100.59.193 master02 <none> <none>
calico-system csi-node-driver-jbmmh 2/2 Running 0 12m 10.100.235.1 master03 <none> <none>
calico-system csi-node-driver-lds6w 2/2 Running 0 12m 10.100.241.66 master01 <none> <none>
calico-system csi-node-driver-vgzdl 2/2 Running 0 12m 10.100.30.65 worker02 <none> <none>
tigera-operator tigera-operator-76ff79f7fd-tsqzs 1/1 Running 0 28m 10.0.250.7 worker02 <none> <none>
VXLAN隧道配置
#手动配置并持久化
cat >> /etc/sysctl.conf << EOF
net.ipv4.ip_forward = 1
net.ipv6.conf.all.forwarding = 1
net.ipv4.conf.all.proxy_arp = 1
EOF
#生效内核参数
sysctl -p
#检查 VXLAN 内核参数（必须为 1）
[root@master01 ~]# sysctl -a | grep -E "net.ipv4.ip_forward|net.ipv6.conf.all.forwarding|net.ipv4.conf.all.proxy_arp"
net.ipv4.conf.all.proxy_arp = 1
net.ipv4.conf.all.proxy_arp_pvlan = 0
net.ipv4.ip_forward = 1
net.ipv4.ip_forward_update_priority = 1
net.ipv4.ip_forward_use_pmtu = 0
net.ipv6.conf.all.forwarding = 1
kubectl edit ippool -n calico-system default-ipv4-ippool
...
spec:
allowedUses:
- Workload
- Tunnel
blockSize: 26
cidr: 10.100.0.0/16
ipipMode: Never
natOutgoing: true
nodeSelector: all()
vxlanMode: Always
...
[root@master01 game]# kubectl get ippool -n calico-system default-ipv4-ippool -o yaml | grep -A 10 "vxlanMode"
vxlanMode: Always
kubectl delete pod -n calico-system -l k8s-app=calico-node
containerd 配置镜像加速器（觉得下载慢的请看-限Hong Kong Cloud Server）
#创建 containerd 配置文件（如果没有的话）
mkdir -p /etc/containerd
containerd config default > /etc/containerd/config.toml
#步骤 2：修改配置文件，添加镜像加速器
编辑 /etc/containerd/config.toml，找到 [plugins."io.containerd.grpc.v1.cri".registry.mirrors] 段落，添加以下内容：
[plugins."io.containerd.grpc.v1.cri".registry.mirrors]
[plugins."io.containerd.grpc.v1.cri".registry.mirrors."docker.io"]
endpoint = ["https://hub-mirror.c.163.com", "https://mirror.baidubce.com"]
[plugins."io.containerd.grpc.v1.cri".registry.mirrors."quay.io"]
endpoint = ["https://quay-mirror.qiniu.com"]
这几个是全球通用的公共加速器最后重启
systemctl restart containerd
国内阿里云的配置
# 创建 containerd 配置目录（没有则创建）
mkdir -p /etc/containerd
# 生成默认配置文件（覆盖原有文件）
containerd config default > /etc/containerd/config.toml
# 编辑配置文件，找到 [plugins."io.containerd.grpc.v1.cri".registry.mirrors] 段落，删除原有内容，粘贴下面全部配置
[plugins."io.containerd.grpc.v1.cri".registry.mirrors]
# 配置 DockerHub 全球镜像
[plugins."io.containerd.grpc.v1.cri".registry.mirrors."docker.io"]
endpoint = ["https://docker.mirrors.ustc.edu.cn", "https://hub-mirror.c.163.com"]
# 配置 Calico 镜像
[plugins."io.containerd.grpc.v1.cri".registry.mirrors."quay.io"]
endpoint = ["https://quay.mirrors.ustc.edu.cn"]
# 配置 K8S官方镜像
[plugins."io.containerd.grpc.v1.cri".registry.mirrors."k8s.gcr.io"]
endpoint = ["https://gcr.mirrors.ustc.edu.cn/google-containers"]
# 配置 GCR官方镜像
[plugins."io.containerd.grpc.v1.cri".registry.mirrors."gcr.io"]
endpoint = ["https://gcr.mirrors.ustc.edu.cn"]
最后重启服务生效（国内所有节点执行）
systemctl daemon-reload && systemctl restart containerd
可用去除污点（如果觉得配置不够用-不推荐）
# 去除master01污点
kubectl taint nodes k8s-master01 node-role.kubernetes.io/master:NoSchedule-
# 去除master02污点
kubectl taint nodes k8s-master02 node-role.kubernetes.io/master:NoSchedule-
# 去除master03污点
kubectl taint nodes k8s-master03 node-role.kubernetes.io/master:NoSchedule-
==============================end============================
温馨提示:
如果出现镜像下载失败的情况，要手动拉取镜像导入！
19网络插件falnnel部署案例（calico和falnnel二选一）
1. 创建kube-flannel.yaml
---
apiVersion: policy/v1beta1
kind: PodSecurityPolicy
metadata:
name: psp.flannel.unprivileged
annotations:
seccomp.security.alpha.kubernetes.io/allowedProfileNames: docker/default
seccomp.security.alpha.kubernetes.io/defaultProfileName: docker/default
apparmor.security.beta.kubernetes.io/allowedProfileNames: runtime/default
apparmor.security.beta.kubernetes.io/defaultProfileName: runtime/default
spec:
privileged: false
volumes:
- configMap
- secret
- emptyDir
- hostPath
allowedHostPaths:
- pathPrefix: "/etc/cni/net.d"
- pathPrefix: "/etc/kube-flannel"
- pathPrefix: "/run/flannel"
readOnlyRootFilesystem: false
runAsUser:
rule: RunAsAny
supplementalGroups:
rule: RunAsAny
fsGroup:
rule: RunAsAny
allowPrivilegeEscalation: false
defaultAllowPrivilegeEscalation: false
allowedCapabilities: ['NET_ADMIN', 'NET_RAW']
defaultAddCapabilities: []
requiredDropCapabilities: []
hostNetwork: true
hostPorts:
- min: 0
max: 65535
hostIPC: false
hostPID: false
seLinux:
rule: 'RunAsAny'
---
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1
metadata:
name: flannel
rules:
- apiGroups: ['extensions']
resources: ['podsecuritypolicies']
verbs: ['use']
resourceNames: ['psp.flannel.unprivileged']
- apiGroups:
- ""
resources:
- pods
verbs:
- get
- apiGroups:
- ""
resources:
- nodes
verbs:
- list
- watch
- apiGroups:
- ""
resources:
- nodes/status
verbs:
- patch
---
kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
name: flannel
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: flannel
subjects:
- kind: ServiceAccount
name: flannel
namespace: kube-flannel
---
apiVersion: v1
kind: ServiceAccount
metadata:
name: flannel
namespace: kube-flannel
---
kind: ConfigMap
apiVersion: v1
metadata:
name: kube-flannel-cfg
namespace: kube-flannel
labels:
tier: node
app: flannel
data:
cni-conf.json: |
{
"name": "cbr0",
"cniVersion": "0.3.1",
"plugins": [
{
"type": "flannel",
"delegate": {
"hairpinMode": true,
"isDefaultGateway": true
}
},
{
"type": "portmap",
"capabilities": {
"portMappings": true
}
}
]
}
net-conf.json: |
{
"Network": "10.100.0.0/16",
"Backend": {
"Type": "vxlan"
}
}
---
apiVersion: apps/v1
kind: DaemonSet
metadata:
name: kube-flannel-ds
namespace: kube-flannel
labels:
tier: node
app: flannel
spec:
selector:
matchLabels:
app: flannel
template:
metadata:
labels:
tier: node
app: flannel
spec:
affinity:
nodeAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
nodeSelectorTerms:
- matchExpressions:
- key: kubernetes.io/os
operator: In
values:
- linux
hostNetwork: true
priorityClassName: system-node-critical
tolerations:
- operator: Exists
effect: NoSchedule
serviceAccountName: flannel
initContainers:
- name: install-cni-plugin
image: docker.io/flannel/flannel-cni-plugin:v1.4.1
command:
- cp
args:
- -f
- /flannel
- /opt/cni/bin/flannel
volumeMounts:
- name: cni-plugin
mountPath: /opt/cni/bin
- name: install-cni
image: docker.io/flannel/flannel:v0.25.4
command:
- cp
args:
- -f
- /etc/kube-flannel/cni-conf.json
- /etc/cni/net.d/10-flannel.conflist
volumeMounts:
- name: cni
mountPath: /etc/cni/net.d
- name: flannel-cfg
mountPath: /etc/kube-flannel/
containers:
- name: kube-flannel
image: docker.io/flannel/flannel:v0.25.4
command:
- /opt/bin/flanneld
args:
- --ip-masq
- --kube-subnet-mgr
resources:
requests:
cpu: "100m"
memory: "50Mi"
limits:
cpu: "100m"
memory: "50Mi"
securityContext:
privileged: false
capabilities:
add: ["NET_ADMIN", "NET_RAW"]
env:
- name: POD_NAME
valueFrom:
fieldRef:
fieldPath: metadata.name
- name: POD_NAMESPACE
valueFrom:
fieldRef:
fieldPath: metadata.namespace
volumeMounts:
- name: run
mountPath: /run/flannel
- name: flannel-cfg
mountPath: /etc/kube-flannel/
- name: xtables-lock
mountPath: /run/xtables.lock
readOnly: false
volumes:
- name: run
hostPath:
path: /run/flannel
- name: cni-plugin
hostPath:
path: /opt/cni/bin
- name: cni
hostPath:
path: /etc/cni/net.d
- name: flannel-cfg
configMap:
name: kube-flannel-cfg
- name: xtables-lock
hostPath:
path: /run/xtables.lock
type: FileOrCreate
updateStrategy:
type: RollingUpdate
rollingUpdate:
maxUnavailable: 1
2.部署Flannel
[root@master01 ~]# kubectl apply -f kube-flannel.yml
3.查看flannel 组件
[root@master01 ~]# kubectl get pods -A -o wide
4.查看集群是否正常
[root@master01 bin]# kubectl get nodes
NAME STATUS ROLES AGE VERSION
master01 Ready <none> 3h10m v1.30.2
master02 Ready <none> 169m v1.30.2
master03 Ready <none> 169m v1.30.2
worker01 Ready <none> 157m v1.30.2
worker02 Ready <none> 157m v1.30.2
20启动deployment资源测试
5. 下载镜像
链接: https://pan.baidu.com/s/1k4yZHQoCawwvsUkKRbtBKw?pwd=v2kf
6. 导入镜像worker节点
[root@worker02 ~]# ctr -n k8s.io images import testgame-v0.1.tar
unpacking docker.io/library/testgame:v0.1 (sha256:f557641e74e77b5d116174796fdcda090b45581817d84593bd1e87a276f7286f)...done
[root@worker02 ~]# ctr -n k8s.io images ls | grep -E "testgame|v0.1"
docker.io/library/testgame:v0.1 application/vnd.oci.image.manifest.v1+json sha256:f557641e74e77b5d116174796fdcda090b45581817d84593bd1e87a276f7286f 90.1 MiB linux/amd64 io.cri-containerd.image=managed
7. 启动deploy
[root@master01 ~]# cat deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
name: game-static
labels:
app: game-static
spec:
replicas: 2
selector:
matchLabels:
app: game-static
template:
metadata:
labels:
app: game-static
spec:
containers:
- name: game-static
image: testgame:v0.1
---
apiVersion: v1
kind: Service
metadata:
name: game-static-svc
spec:
selector:
app: game-static
type: ClusterIP
ports:
- port: 8090
targetPort: 8090
8.验证Pod是否可以正常启动
[root@master01 ~]# kubectl get pods,svc -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
pod/game-static-7db8f5dcb7-48pmh 1/1 Running 0 3m2s 10.100.5.23 worker01 <none> <none>
pod/game-static-7db8f5dcb7-fdft6 1/1 Running 0 3m2s 10.100.30.77 worker02 <none> <none>
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTOR
service/game-static-svc ClusterIP 10.200.7.244 <none> 8090/TCP 3m2s app=game-static
service/kubernetes ClusterIP 10.200.0.1 <none> 443/TCP 15d <none>
9. 测试访问
[root@master01 ~]# curl 10.200.7.244:8090
<!DOCTYPE html>
<html lang="zh-CN">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>经典小游戏合集 - 点击开始游玩</title>
<style>
* {margin:0;padding:0;box-sizing:border-box;}
body {background:#1e1e1e;padding:20px;font-family:Arial, "微软雅黑", sans-serif;}
h1 {text-align:center;color:#fff;margin-bottom:30px;font-size:28px;}
.game-list {width:100%;max-width:1200px;margin:0 auto;display:flex;flex-wrap:wrap;justify-content:center;gap:15px;}
.game-item {width:160px;height:60px;line-height:60px;background:#2d7dff;text-align:center;border-radius:8px;}
.game-item a {display:block;width:100%;height:100%;color:#fff;text-decoration:none;font-size:16px;font-weight:bold;}
.game-item:hover {background:#1a66e0;transform:scale(1.03);transition:all 0.2s;}
</style>
</head>
<body>
<h1>🎮 经典小游戏合集 🎮</h1>
<div class="game-list">
<div class="game-item"><a href="/html/zhiwuVSjiangshi/">植物VS僵尸</a></div>
</div>
</body>
</html>
10.删除资源
[root@master01 ~]# kubectl delete -f deployment.yaml
deployment.apps "game-static" deleted
service "game-static-svc" deleted
更多推荐
13
0- 0
已为社区贡献5条内容
所有评论(0)