部署3主3从的kubernetes1.21.0高可用集群环境
参考地址：https://www.cnblogs.com/superlinux/p/14676959.html
1、主机操作系统说明
| 序号 | 操作系统及版本 | 备注 |
|---|---|---|
| 1 | centos7.6 |
2、主机硬件配置说明
| 需求 | CPU | 内存 | 硬盘 | 角色 | 主机名 | ip地址 | 备注 |
|---|---|---|---|---|---|---|---|
| 值 | 4C | 8G | 100G | master | k8s-master01 | 192.168.10.21 | |
| 值 | 4C | 8G | 100G | master | k8s-master02 | 192.168.10.22 | |
| 值 | 4C | 8G | 100G | master | k8s-master03 | 192.168.10.23 | |
| 值 | 4C | 8G | 100G | worker（node） | k8s-worker01 | 192.168.10.24 | |
| 值 | 4C | 8G | 100G | worker（node） | k8s-worker02 | 192.168.10.25 | |
| 值 | 4C | 8G | 100G | worker（node） | k8s-worker03 | 192.168.10.26 | |
| k8s-master-lb | 192.168.10.100 |
| 序号 | 主机名 | 功能 | 备注 |
|---|---|---|---|
| 1 | master01 | haproxy、keepalived | keepalived主节点 |
| 2 | master02 | haproxy、keepalived | keepalived从节点 |
| 3 | master03 | haproxy、keepalived | keepalived从节点 |
花里胡哨的美化配置
#命令行优化：
echo "export PS1='\[\033[01;31m\]\u\[\033[00m\]@\[\033[01;32m\]\h\[\033[00m\][\[\033[01;33m\]\t\[\033[00m\]]:\[\033[01;34m\]\w\[\033[00m\]$ '" >>/etc/profile
source /etc/profile
#历史记录优化：
export HISTTIMEFORMAT='%F %T '
echo "export HISTTIMEFORMAT='%F %T '" >>/etc/profile
source /etc/profile
3、主机配置
3.1、配置yum源，所有主机都配置
采用阿里云源
rm -rf /etc/yum.repos.d/*
cd /etc/yum.repos.d/
curl -o /etc/yum.repos.d/CentOS-Base.repo https://mirrors.aliyun.com/repo/Centos-7.repo
yum install -y yum-utils device-mapper-persistent-data lvm2
yum-config-manager --add-repo https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo
cat <<EOF > /etc/yum.repos.d/kubernetes.repo
[kubernetes]
name=Kubernetes
baseurl=https://mirrors.aliyun.com/kubernetes/yum/repos/kubernetes-el7-x86_64/
enabled=1
gpgcheck=1
repo_gpgcheck=1
gpgkey=https://mirrors.aliyun.com/kubernetes/yum/doc/yum-key.gpg https://mirrors.aliyun.com/kubernetes/yum/doc/rpm-package-key.gpg
EOF
sed -i -e '/mirrors.cloud.aliyuncs.com/d' -e '/mirrors.aliyuncs.com/d' /etc/yum.repos.d/CentOS-Base.repo
yum clean all
yum install -y epel-release
#安装必备工具：
#必备工具安装
yum install wget jq psmisc vim net-tools telnet yum-utils device-mapper-persistent-data lvm2 git -y
下载安装所有的源码文件，后面需要用到
cd /root/
git clone https://github.com/dotbalo/k8s-ha-install.git
#如果无法下载请使用下面的重试：
git clone https://gitee.com/dukuan/k8s-ha-install.git
3.2、修改主机名，配置hosts本地解析
master01为例，其他主机均配置，注意主机名
hostnamectl set-hostname k8s-master01
bash
cat >> /etc/hosts <<EOF
192.168.3.31 k8s-master01
192.168.3.32 k8s-master02
192.168.3.33 k8s-master03
192.168.3.34 k8s-worker01
192.168.3.35 k8s-worker02
192.168.3.36 k8s-worker03
192.168.3.100 k8s-master-lb
EOF
cat /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.3.31 k8s-master01
192.168.3.32 k8s-master02
192.168.3.33 k8s-master03
192.168.3.34 k8s-worker01
192.168.3.35 k8s-worker02
192.168.3.36 k8s-worker03
192.168.3.100 k8s-master-lb
完成以后在master01上测试连通性
[root@master01 ~]# ping k8s-worker01
[root@master01 ~]# ping k8s-worker02
#以下以master01结果为例
[root@master01 ~]# ping worker01
PING worker01 (192.168.10.22) 56(84) bytes of data.
64 bytes from worker01 (192.168.10.22): icmp_seq=1 ttl=64 time=0.652 ms
64 bytes from worker01 (192.168.10.22): icmp_seq=2 ttl=64 time=0.430 ms
^C
--- worker01 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1065ms
rtt min/avg/max/mdev = 0.430/0.541/0.652/0.111 ms
[root@master01 ~]# ping worker02
PING worker02 (192.168.10.23) 56(84) bytes of data.
64 bytes from worker02 (192.168.10.23): icmp_seq=1 ttl=64 time=0.774 ms
64 bytes from worker02 (192.168.10.23): icmp_seq=2 ttl=64 time=0.444 ms
^C
--- worker02 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1019ms
rtt min/avg/max/mdev = 0.444/0.609/0.774/0.165 ms
------
3.3、所有节点优化
master01为例，其他主机均配置，配置完成后 重启主机
#所有节点关闭防火墙、selinux、dnsmasq、swap。服务器配置如下：
systemctl disable --now firewalld
systemctl disable --now dnsmasq
setenforce 0
sed -i 's#SELINUX=enforcing#SELINUX=disabled#g' /etc/sysconfig/selinux
sed -i 's#SELINUX=enforcing#SELINUX=disabled#g' /etc/selinux/config
#关闭swap分区
swapoff -a && sysctl -w vm.swappiness=0
sed -ri '/^[^#]*swap/s@^@#@' /etc/fstab
#安装ntpdate
rpm -ivh http://mirrors.wlnmp.com/centos/wlnmp-release-centos.noarch.rpm
#添加计划任务
yum install -y ntpdate
echo '*/5 * * * * ntpdate cn.pool.ntp.org' >>/var/spool/cron/root
systemctl restart crond
ntpdate time2.aliyun.com
#所有节点同步时间。时间同步配置如下：
ln -sf /usr/share/zoneinfo/Asia/Shanghai /etc/localtime
echo 'Asia/Shanghai' >/etc/timezone
ntpdate time2.aliyun.com
# 加入到crontab
*/5 * * * * /usr/sbin/ntpdate time2.aliyun.com
#limit优化
ulimit -SHn 65535
cat <<EOF >> /etc/security/limits.conf
* soft nofile 655360
* hard nofile 131072
* soft nproc 655350
* hard nproc 655350
* soft memlock unlimited
* hard memlock unlimited
EOF
3.4、配置免密[中控机操作:master01]
#Master01节点免密钥登录其他节点，安装过程中生成配置文件和证书均在Master01上操作，集群管理也在Master01上操作，阿里云或者AWS上需要单独一台kubectl服务器。密钥配置如下：
cd /root
ssh-keygen -t rsa
for i in k8s-master01 k8s-master02 k8s-master03 k8s-worker01 k8s-worker02 k8s-worker03;do ssh-copy-id -i .ssh/id_rsa.pub $i;done
3.5、升级内核
#启用 ELRepo 只需要执行命令：
yum -y install elrepo-release
# 列出可用的内核相关包：
yum --disablerepo="*" --enablerepo="elrepo-kernel" list available
yum --disablerepo="*" --enablerepo="elrepo-kernel" list available --showduplicates #查看所有版本
# 根据上述查询结果，安装内核相关包
# 安装新内核
yum --disablerepo=\* --enablerepo=elrepo-kernel install -y kernel-ml.x86_64
#kernel-core、kernel-modules 与 kernel 依赖自动更新
# 安装新内核相关软件
yum --disablerepo=\* --enablerepo=elrepo-kernel install -y kernel-ml-devel kernel-ml-tools kernel-ml-tools-libs kernel-ml-tools-libs-devel kernel-ml-headers --skip-broken
#查看系统安装的全部内核：
root@k8s-master01[18:08:45]:~$ grubby --info=ALL
index=0
kernel=/boot/vmlinuz-6.6.11-1.el7.elrepo.x86_64
args="ro crashkernel=auto rd.lvm.lv=centos/root rhgb quiet LANG=en_US.UTF-8"
root=/dev/mapper/centos-root
initrd=/boot/initramfs-6.6.11-1.el7.elrepo.x86_64.img
title=CentOS Linux (6.6.11-1.el7.elrepo.x86_64) 7 (Core)
index=1
kernel=/boot/vmlinuz-3.10.0-957.el7.x86_64
args="ro crashkernel=auto rd.lvm.lv=centos/root rhgb quiet LANG=en_US.UTF-8"
root=/dev/mapper/centos-root
initrd=/boot/initramfs-3.10.0-957.el7.x86_64.img
title=CentOS Linux (3.10.0-957.el7.x86_64) 7 (Core)
index=2
kernel=/boot/vmlinuz-0-rescue-6b99fdbc99164b2d8a41e9891d315802
args="ro crashkernel=auto rd.lvm.lv=centos/root rhgb quiet"
root=/dev/mapper/centos-root
initrd=/boot/initramfs-0-rescue-6b99fdbc99164b2d8a41e9891d315802.img
title=CentOS Linux (0-rescue-6b99fdbc99164b2d8a41e9891d315802) 7 (Core)
index=3
non linux entry
You have new mail in /var/spool/mail/root
#使用路径来指定内核，可以使用 --set-default=kernel-path
root@k8s-master01[18:18:16]:~$grubby --set-default=/boot/vmlinuz-6.6.11-1.el7.elrepo.x86_64
root@k8s-master01[18:18:16]:~$ grubby --default-kernel
/boot/vmlinuz-6.6.11-1.el7.elrepo.x86_64
#重启
reboot
3.6、所有节点安装ipvsadm
yum install ipvsadm ipset sysstat conntrack libseccomp -y
#所有节点配置ipvs模块，在内核4.19+版本nf_conntrack_ipv4已经改为nf_conntrack， 4.18以下使用nf_conntrack_ipv4即可：
modprobe -- ip_vs
modprobe -- ip_vs_rr
modprobe -- ip_vs_wrr
modprobe -- ip_vs_sh
modprobe -- nf_conntrack
#创建 /etc/modules-load.d/ipvs.conf 并加入以下内容：
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
#设置为开机启动
systemctl enable --now systemd-modules-load.service
3.7、k8s内核优化
#开启一些k8s集群中必须的内核参数，所有节点配置k8s内核：
cat <<EOF > /etc/sysctl.d/k8s.conf
net.ipv4.ip_forward = 1
net.bridge.bridge-nf-call-iptables = 1
net.bridge.bridge-nf-call-ip6tables = 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
#所有节点配置完内核后，重启服务器，保证重启后内核依旧加载
reboot
lsmod | grep --color=auto -e ip_vs -e nf_conntrack
#重启后结果如下代表正常：
root@k8s-master01[17:19:15]:~$ lsmod | grep --color=auto -e ip_vs -e nf_conntrack
ip_vs_ftp 16384 0
nf_nat 32768 1 ip_vs_ftp
ip_vs_sed 16384 0
ip_vs_nq 16384 0
ip_vs_fo 16384 0
ip_vs_sh 16384 0
ip_vs_dh 16384 0
ip_vs_lblcr 16384 0
ip_vs_lblc 16384 0
ip_vs_wrr 16384 0
ip_vs_rr 16384 0
ip_vs_wlc 16384 0
ip_vs_lc 16384 0
ip_vs 151552 24 ip_vs_wlc,ip_vs_rr,ip_vs_dh,ip_vs_lblcr,ip_vs_sh,ip_vs_fo,ip_vs_nq,ip_vs_lblc,ip_vs_wrr,ip_vs_lc,ip_vs_sed,ip_vs_ftp
nf_conntrack 143360 2 nf_nat,ip_vs
nf_defrag_ipv6 20480 1 nf_conntrack
nf_defrag_ipv4 16384 1 nf_conntrack
libcrc32c 16384 4 nf_conntrack,nf_nat,xfs,ip_vs
3.8、基本组件安装
3.8.1、所有节点安装 docker-ce 20.10
yum install -y docker-ce-20.10.6-* docker-ce-cli-20.10.6-*.x86_64
rm -f /etc/docker/*
sudo mkdir -p /etc/docker
sudo tee /etc/docker/daemon.json <<-'EOF'
{
"registry-mirrors": ["https://ajvcw8qn.mirror.aliyuncs.com"],
"exec-opts": ["native.cgroupdriver=systemd"]
}
EOF
sudo systemctl daemon-reload
sudo systemctl restart docker
systemctl enable --now docker.service
3.8.2、所有机器安装k8s组件kubeadm
yum list kubeadm.x86_64 --showduplicates | sort -r
#所有节点安装最新版本kubeadm：
yum install kubeadm-1.21* kubelet-1.21* kubectl-1.21* -y
#默认配置的pause镜像使用gcr.io仓库，国内可能无法访问，所以这里配置Kubelet使用阿里云的pause镜像
cat >/etc/sysconfig/kubelet<<EOF
KUBELET_EXTRA_ARGS="--cgroup-driver=systemd --pod-infra-container-image=registry.cn-hangzhou.aliyuncs.com/google_containers/pause-amd64:3.2"
EOF
#设置开机启动
systemctl daemon-reload
systemctl enable --now kubelet
3.8.3、安装高可用组件[master相关服务器执行]
#所有Master节点通过yum安装HAProxy和KeepAlived：
root@k8s-master01[17:44:47]:~$ yum install keepalived haproxy -y
#配置HAProxy：
#所有Master节点配置HAProxy（详细配置参考HAProxy文档，所有Master节点的HAProxy配置相同）：
mkdir /etc/haproxy
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
timeout connect 5000
timeout client 50000
timeout server 50000
timeout http-request 15s
timeout http-keep-alive 15s
frontend monitor-in
bind *:33305
mode http
option httplog
monitor-uri /monitor
frontend k8s-master
bind 0.0.0.0:16443
bind 127.0.0.1:16443
mode tcp
option tcplog
tcp-request inspect-delay 5s
default_backend k8s-master
backend k8s-master
mode tcp
option tcplog
option tcp-check
balance roundrobin
default-server inter 10s downinter 5s rise 2 fall 2 slowstart 60s maxconn 250 maxqueue 256 weight 100
server k8s-master01 192.168.3.31:6443 check
server k8s-master02 192.168.3.32:6443 check
server k8s-master03 192.168.3.33:6443 check
EOF
#所有Master节点配置KeepAlived，配置不一样，注意区分
#[root@k8s-master01 pki]# vim /etc/keepalived/keepalived.conf ，注意每个节点的IP和网卡（interface参数）
#注意修改配置，下面IP替换为master的IP地址：
server k8s-master01 192.168.3.31:6443 check
server k8s-master02 192.168.3.32:6443 check
server k8s-master03 192.168.3.33:6443 check
#配置keepalived
#所有Master节点配置KeepAlived，配置不一样，注意区分
#每台服务器 优先级必须不同 priority 100 其他机器设置为 99 98
#master01 配置：
[root@k8s-master01 pki]# mkdir -p /etc/keepalived
[root@k8s-master01 pki]# cat >/etc/keepalived/keepalived.conf<<"EOF"
! Configuration File for keepalived
global_defs {
router_id LVS_DEVEL
script_user root
enable_script_security
}
vrrp_script chk_apiserver {
script "/etc/keepalived/check_apiserver.sh"
interval 5
weight -5
fall 2
rise 1
}
vrrp_instance VI_1 {
state MASTER
interface eth0
mcast_src_ip 192.168.3.31
virtual_router_id 51
priority 100
advert_int 2
authentication {
auth_type PASS
auth_pass K8SHA_KA_AUTH
}
virtual_ipaddress {
192.168.3.100
}
track_script {
chk_apiserver
}
}
EOF
#Master02 配置：
[root@k8s-master02 pki]# cat >/etc/keepalived/keepalived.conf<<"EOF"
! Configuration File for keepalived
global_defs {
router_id LVS_DEVEL
script_user root
enable_script_security
}
vrrp_script chk_apiserver {
script "/etc/keepalived/check_apiserver.sh"
interval 5
weight -5
fall 2
rise 1
}
vrrp_instance VI_1 {
state BACKUP
interface eth0
mcast_src_ip 192.168.3.32
virtual_router_id 51
priority 99
advert_int 2
authentication {
auth_type PASS
auth_pass K8SHA_KA_AUTH
}
virtual_ipaddress {
192.168.3.100
}
track_script {
chk_apiserver
}
}
EOF
#Master03 配置：
[root@k8s-master03 pki]# cat >/etc/keepalived/keepalived.conf<<"EOF"
! Configuration File for keepalived
global_defs {
router_id LVS_DEVEL
script_user root
enable_script_security
}
vrrp_script chk_apiserver {
script "/etc/keepalived/check_apiserver.sh"
interval 5
weight -5
fall 2
rise 1
}
vrrp_instance VI_1 {
state BACKUP
interface eth0
mcast_src_ip 192.168.3.33
virtual_router_id 51
priority 98
advert_int 2
authentication {
auth_type PASS
auth_pass K8SHA_KA_AUTH
}
virtual_ipaddress {
192.168.3.100
}
EOF
#快捷办法[变量获取本机IP]：
host=$(hostname -i)
cat >/etc/keepalived/keepalived.conf<<EOF
! Configuration File for keepalived
global_defs {
router_id LVS_DEVEL
script_user root
enable_script_security
}
vrrp_script chk_apiserver {
script "/etc/keepalived/check_apiserver.sh"
interval 5
weight -5
fall 2
rise 1
}
vrrp_instance VI_1 {
state MASTER
interface eth0
mcast_src_ip $(hostname -i)
virtual_router_id 51
priority 101
advert_int 2
authentication {
auth_type PASS
auth_pass K8SHA_KA_AUTH
}
virtual_ipaddress {
192.168.3.100
}
track_script {
chk_apiserver
}
}
EOF
3.8.4、健康检查配置[所有master服务器添加健康检查脚本]
cat > /etc/keepalived/check_apiserver.sh <<"EOF"
#!/bin/bash
err=0
for k in $(seq 1 3)
do
check_code=$(pgrep haproxy)
if [[ $check_code == "" ]]; then
err=$(expr $err + 1)
sleep 1
continue
else
err=0
break
fi
done
if [[ $err != "0" ]]; then
echo "systemctl stop keepalived"
/usr/bin/systemctl stop keepalived
exit 1
else
exit 0
fi
EOF
chmod +x /etc/keepalived/check_apiserver.sh
3.8.5、启动haproxy和keepalived[每台master启用]
systemctl daemon-reload
systemctl enable --now haproxy
systemctl enable --now keepalived
3.8.6、测试haproxy与keepalived是否正常
重要：如果安装了keepalived和haproxy，需要测试keepalived是否是正常的
所以这里需要测试VIP是否通
root@k8s-master01[18:19:31]:~$ ping 192.168.3.100 -c 4
PING 192.168.3.100 (192.168.3.100) 56(84) bytes of data.
64 bytes from 192.168.3.100: icmp_seq=1 ttl=64 time=0.421 ms
64 bytes from 192.168.3.100: icmp_seq=2 ttl=64 time=0.289 ms
64 bytes from 192.168.3.100: icmp_seq=3 ttl=64 time=0.321 ms
64 bytes from 192.168.3.100: icmp_seq=4 ttl=64 time=0.232 ms
--- 192.168.3.100 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3080ms
rtt min/avg/max/mdev = 0.232/0.315/0.421/0.071 ms
You have new mail in /var/spool/mail/root
root@k8s-master02[17:52:24]:~$ ping 192.168.3.100 -c 4
PING 192.168.3.100 (192.168.3.100) 56(84) bytes of data.
64 bytes from 192.168.3.100: icmp_seq=1 ttl=64 time=0.458 ms
64 bytes from 192.168.3.100: icmp_seq=2 ttl=64 time=0.344 ms
64 bytes from 192.168.3.100: icmp_seq=3 ttl=64 time=0.253 ms
64 bytes from 192.168.3.100: icmp_seq=4 ttl=64 time=0.373 ms
--- 192.168.3.100 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3093ms
rtt min/avg/max/mdev = 0.253/0.357/0.458/0.073 ms
You have new mail in /var/spool/mail/root
root@k8s-master03[17:52:24]:~$ ping 192.168.3.100 -c 4
PING 192.168.3.100 (192.168.3.100) 56(84) bytes of data.
64 bytes from 192.168.3.100: icmp_seq=1 ttl=64 time=0.079 ms
64 bytes from 192.168.3.100: icmp_seq=2 ttl=64 time=0.054 ms
64 bytes from 192.168.3.100: icmp_seq=3 ttl=64 time=0.058 ms
64 bytes from 192.168.3.100: icmp_seq=4 ttl=64 time=0.055 ms
--- 192.168.3.100 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3094ms
rtt min/avg/max/mdev = 0.054/0.061/0.079/0.012 ms
You have new mail in /var/spool/mail/root
注意： 如果ping不通且telnet没有出现 ] ，则认为VIP不可以，不可在继续往下执行，需要排查keepalived的问题，比如防火墙和selinux，haproxy和keepalived的状态，监听端口等
所有节点查看防火墙状态必须为disable和inactive：systemctl status firewalld
所有节点查看selinux状态，必须为disable：getenforce
master节点查看haproxy和keepalived状态：systemctl status keepalived haproxy
master节点查看监听端口：netstat -lntp
排查思路：
keepalived的问题，比如防火墙和selinux，haproxy和keepalived的状态，监听端口等
所有节点查看防火墙状态必须为disable和inactive：systemctl status firewalld
所有节点查看selinux状态，必须为disable：getenforce
master节点查看haproxy和keepalived状态：systemctl status keepalived haproxy
master节点查看监听端口：netstat -lntp
4、kubernetes集群初始化
Master01节点创建 kubeadm-config.yaml 配置文件如下：
Master01：（# 注意，如果不是高可用集群，192.168.3.100:16443改为master01的地址，16443改为apiserver的端口，默认是6443，注意更改v1.18.5自己服务器kubeadm的版本：kubeadm version）
#查看办法：
kubectl version
root@k8s-master01[18:25:48]:~$ kubectl version
Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.0", GitCommit:"cb303e613a121a29364f75cc67d3d580833a7479", GitTreeState:"clean", BuildDate:"2021-04-08T16:31:21Z", GoVersion:"go1.16.1", Compiler:"gc", Platform:"linux/amd64"}
因为安装的版本是 GitVersion:"v1.21.0"
下面的yaml文件中的对应版本需要改为 v1.21.0
root@k8s-master01[18:28:03]:~$ cat kubeadm-config.yaml
apiVersion: kubeadm.k8s.io/v1beta2
bootstrapTokens:
- groups:
- system:bootstrappers:kubeadm:default-node-token
token: 7t2weq.bjbawausm0jaxury
ttl: 24h0m0s
usages:
- signing
- authentication
kind: InitConfiguration
localAPIEndpoint:
advertiseAddress: 192.168.3.31
bindPort: 6443
nodeRegistration:
criSocket: /var/run/dockershim.sock
name: k8s-master01
taints:
- effect: NoSchedule
key: node-role.kubernetes.io/master
---
apiServer:
certSANs:
- 192.168.3.100
timeoutForControlPlane: 4m0s
apiVersion: kubeadm.k8s.io/v1beta2
certificatesDir: /etc/kubernetes/pki
clusterName: kubernetes
controlPlaneEndpoint: 192.168.3.100:16443
controllerManager: {}
dns:
type: CoreDNS
etcd:
local:
dataDir: /var/lib/etcd
imageRepository: registry.cn-hangzhou.aliyuncs.com/google_containers
kind: ClusterConfiguration
kubernetesVersion: v1.21.0
networking:
dnsDomain: cluster.local
podSubnet: 10.244.0.0/16
serviceSubnet: 10.96.0.0/12
scheduler: {}
#更新kubeadm文件: kubeadm-config.yaml
kubeadm config migrate --old-config kubeadm-config.yaml --new-config new.yaml
#将new.yaml文件复制到其他master节点，之后所有Master节点提前下载镜像，可以节省初始化时间：
for i in k8s-master02 k8s-master03; do scp new.yaml $i:/root/; done
#在其他master节点提前下载镜像，用于解决初始化时间
kubeadm config images pull --config /root/new.yaml
systemctl enable --now kubelet
#执行kubeadm config images pull --config /root/new.yaml如果出现如下报错
[config/images] Pulled registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.4.1
[config/images] Pulled registry.cn-hangzhou.aliyuncs.com/google_containers/etcd:3.4.13-0
failed to pull image "registry.cn-hangzhou.aliyuncs.com/google_containers/coredns/coredns:v1.8.0": output: Error response from daemon: manifest for registry.cn-hangzhou.aliyuncs.com/google_containers/coredns/coredns:v1.8.0 not found: manifest unknown: manifest unknown
, error: exit status 1
To see the stack trace of this error execute with --v=5 or higher
#coredns如果没有成功
出现ImagePullBackOff：
coredns-57d4cbf879-gnh6j 0/1 ImagePullBackOff 0 6m
coredns-57d4cbf879-z79bt 0/1 ImagePullBackOff 0 6m
#请所有节点执行，用于下载镜像即可：
docker pull registry.cn-beijing.aliyuncs.com/dotbalo/coredns:1.8.0
docker tag registry.cn-beijing.aliyuncs.com/dotbalo/coredns:1.8.0 registry.cn-hangzhou.aliyuncs.com/google_containers/coredns/coredns:v1.8.0
#再次查看就会自动拉起
coredns-57d4cbf879-gnh6j 1/1 Running 0 16h
coredns-57d4cbf879-z79bt 1/1 Running 0 16h
4.2、 master01初始化
#master01节点执行初始化：
kubeadm init --config /root/new.yaml --upload-certs
#如果初始化失败，重置后再次初始化，命令如下：
kubeadm reset -f ; ipvsadm --clear ; rm -rf ~/.kube
关键提示信息：
You should now deploy a pod network to the cluster.
Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at:
https://kubernetes.io/docs/concepts/cluster-administration/addons/
You can now join any number of the control-plane node running the following command on each as root:
[其他master加入集群]
kubeadm join 192.168.3.100:16443 --token 7t2weq.bjbawausm0jaxury \
--discovery-token-ca-cert-hash sha256:aeb438bb077768d6626fbc5f2ff61a903bfea24c2eaaa3fde49bace433176384 \
--control-plane --certificate-key 530a5f56ce32e4ab69b384f41e6165327e23577f4924558b36efb6bb08a883e5
Please note that the certificate-key gives access to cluster sensitive data, keep it secret!
As a safeguard, uploaded-certs will be deleted in two hours; If necessary, you can use
"kubeadm init phase upload-certs --upload-certs" to reload certs afterward.
Then you can join any number of worker nodes by running the following on each as root:
[其他node加入集群]
kubeadm join 192.168.3.100:16443 --token 7t2weq.bjbawausm0jaxury \
--discovery-token-ca-cert-hash sha256:aeb438bb077768d6626fbc5f2ff61a903bfea24c2eaaa3fde49bace433176384
#优化
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config
cat <<EOF >> /root/.bashrc
export KUBECONFIG=/etc/kubernetes/admin.conf
EOF
source /root/.bashrc
4.2、master02 master03 加入master集群
#Token过期后生成新的token：
kubeadm token create --print-join-command
#Master需要生成-certificate-key
root@k8s-master01[15:36:45]:~$ kubeadm init phase upload-certs --upload-certs
[upload-certs] Storing the certificates in Secret "kubeadm-certs" in the "kube-system" Namespace
[upload-certs] Using certificate key:
9b5153fe13fe5a9286eb68fae35311f7357b854a2f8ad925bc7e45b16d2b886e
#其他master加入集群
kubeadm join 192.168.3.100:16443 --token fgtxr1.bz6dw1tci1kbj977 --discovery-token-ca-cert-hash sha256:06ebf46458a41922ff1f5b3bc49365cf3dd938f1a7e3e4a8c8049b5ec5a3aaa5 \
--control-plane --certificate-key 9b5153fe13fe5a9286eb68fae35311f7357b854a2f8ad925bc7e45b16d2b886e
4.3、worker01 worker02 worker03 加入master集群
kubeadm join 192.168.1.160:16443 --token 7t2weq.bjbawausm0jaxury --discovery-token-ca-cert-hash sha256:aeb438bb077768d6626fbc5f2ff61a903bfea24c2eaaa3fde49bace433176384
#过程
root@k8s-work01[15:29:45]:~$ kubeadm join 192.168.3.100:16443 --token 7t2weq.bjbawausm0jaxury \
> --discovery-token-ca-cert-hash sha256:aeb438bb077768d6626fbc5f2ff61a903bfea24c2eaaa3fde49bace433176384
[preflight] Running pre-flight checks
[preflight] Reading configuration from the cluster...
[preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Starting the kubelet
[kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap...
This node has joined the cluster:
* Certificate signing request was sent to apiserver and a response was received.
* The Kubelet was informed of the new secure connection details.
Run 'kubectl get nodes' on the control-plane to see this node join the cluster.
4.4、加入结果预览
root@k8s-master01[16:06:10]:~$ kubectl get nodes
NAME STATUS ROLES AGE VERSION
k8s-master01 NotReady control-plane,master 6m15s v1.21.0
k8s-master02 NotReady control-plane,master 5m23s v1.21.0
k8s-master03 NotReady control-plane,master 4m21s v1.21.0
k8s-worker01 NotReady <none> 11s v1.21.0
k8s-worker02 NotReady <none> 0s v1.21.0
k8s-worker03 NotReady <none> 0s v1.21.0
采用初始化安装方式，所有的系统组件均以容器的方式运行并且在kube-system命名空间内，此时可以查看Pod状态：
root@k8s-master01[20:18:57]:~$ kubectl get pod -n kube-system
NAME READY STATUS RESTARTS AGE
coredns-57d4cbf879-8vs6c 0/1 Pending 0 75m
coredns-57d4cbf879-p99nc 0/1 Pending 0 75m
etcd-k8s-master01 1/1 Running 0 75m
etcd-k8s-master02 1/1 Running 0 4m45s
etcd-k8s-master03 1/1 Running 0 4m23s
kube-apiserver-k8s-master01 1/1 Running 0 75m
kube-apiserver-k8s-master02 1/1 Running 0 4m45s
kube-apiserver-k8s-master03 1/1 Running 0 4m10s
kube-controller-manager-k8s-master01 1/1 Running 1 75m
kube-controller-manager-k8s-master02 1/1 Running 0 4m45s
kube-controller-manager-k8s-master03 1/1 Running 0 4m21s
kube-proxy-2zc6p 1/1 Running 0 4m46s
kube-proxy-djtbn 1/1 Running 0 3m30s
kube-proxy-g2ddr 1/1 Running 0 75m
kube-proxy-gf7w8 1/1 Running 0 3m34s
kube-proxy-mfsbz 1/1 Running 0 3m59s
kube-scheduler-k8s-master01 1/1 Running 1 75m
kube-scheduler-k8s-master02 1/1 Running 0 4m45s
kube-scheduler-k8s-master03 1/1 Running 0 4m19s
#出现 coredns Pending状态，原因是因为没有网络
4.5、Master01节点配置环境变量，用于访问Kubernetes集群：
cat <<EOF >> /root/.bashrc
export KUBECONFIG=/etc/kubernetes/admin.conf
EOF
source /root/.bashrc
5、安装calico网络组件[master01操作]
#运行calicon文件，无需配置改变，直接运行
kubectl create -f https://docs.projectcalico.org/archive/v3.21/manifests/tigera-operator.yaml
#不建议直接使用需要修改，符合kubernetes集群环境才行，因此先下载到本地
#kubectl create -f https://docs.projectcalico.org/archive/v3.21/manifests/custom-resources.yaml
mkdir calicodir
cd calicodir
wget https://docs.projectcalico.org/archive/v3.21/manifests/custom-resources.yaml
#需要修改的地方如下：
[root@master01 calicodir]# cat custom-resources.yaml
# This section includes base Calico installation configuration.
# For more information, see: https://docs.projectcalico.org/v3.21/reference/installation/api#operator.tigera.io/v1.Installation
apiVersion: operator.tigera.io/v1
kind: Installation
metadata:
name: default
spec:
# Configures Calico networking.
calicoNetwork:
# Note: The ipPools section cannot be modified post-install.
ipPools:
- blockSize: 26
cidr: 10.244.0.0/16 ----->这个地方需要做修改
encapsulation: VXLANCrossSubnet
natOutgoing: Enabled
nodeSelector: all()
---
# This section configures the Calico API server.
# For more information, see: https://docs.projectcalico.org/v3.21/reference/installation/api#operator.tigera.io/v1.APIServer
apiVersion: operator.tigera.io/v1
kind: APIServer
metadata:
name: default
spec: {}
#接着对该资源清单文件进行使用
[root@master01 calicodir]# kubectl apply -f custom-resources.yaml
installation.operator.tigera.io/default created
apiserver.operator.tigera.io/default created
##使用如下命令进行查看
[root@master01 calicodir]# kubectl get ns
NAME STATUS AGE
calico-system Active 48s ##创建了一个命名空间
default Active 71m
kube-node-lease Active 71m
kube-public Active 71m
kube-system Active 71m
tigera-operator Active 4m59s
##我们可以查看calico-system命名空间下有哪些pod，运行时间比较长
##官方建议直接使用watch命令查看，直到他全部运行为止
watch kubectl get pods -n calico-system
##我们发现特别慢，原因是因为kubernetes的master节点不允许做工作负载调度，因此需要一个操作，取消污点，命令如下：
kubectl taint nodes --all node-role.kubernetes.io/master-
##接着我们再次查看，等待直到完成，这个过程巨慢
watch kubectl get pods -n calico-system
#最后查看容器和节点状态:
root@k8s-master01[18:34:00]:~$ kubectl get pod -n kube-system
NAME READY STATUS RESTARTS AGE
coredns-6f6b8cc4f6-dd2kf 1/1 Running 0 4h4m
coredns-6f6b8cc4f6-f9gw8 1/1 Running 0 4h4m
etcd-k8s-master01 1/1 Running 5 4h4m
etcd-k8s-master02 1/1 Running 0 4h4m
etcd-k8s-master03 1/1 Running 0 4h4m
kube-apiserver-k8s-master01 1/1 Running 0 4h4m
kube-apiserver-k8s-master02 1/1 Running 0 4h4m
kube-apiserver-k8s-master03 1/1 Running 0 4h4m
kube-controller-manager-k8s-master01 1/1 Running 1 4h4m
kube-controller-manager-k8s-master02 1/1 Running 0 4h4m
kube-controller-manager-k8s-master03 1/1 Running 0 4h4m
kube-proxy-8fpmv 1/1 Running 0 4h3m
kube-proxy-8sw6v 1/1 Running 0 4h3m
kube-proxy-9chjn 1/1 Running 0 4h3m
kube-proxy-ctrth 1/1 Running 0 4h4m
kube-proxy-gsst4 1/1 Running 0 4h4m
kube-proxy-qb9kh 1/1 Running 0 4h3m
kube-scheduler-k8s-master01 1/1 Running 13 4h4m
kube-scheduler-k8s-master02 1/1 Running 4 4h4m
kube-scheduler-k8s-master03 1/1 Running 4 4h4m
You have new mail in /var/spool/mail/root
6、安装dashboard
#1. 安装老版本
cd /root/k8s-ha-install/dashboard/
kubectl create -f .
#2. 安装最新版：
kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.2.0/aio/deploy/recommended.yaml
#授权：
vim admin.yaml
#--------------------------admin.yaml--------------------------#
apiVersion: v1
kind: ServiceAccount
metadata:
name: admin-user
namespace: kube-system
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: admin-user
annotations:
rbac.authorization.kubernetes.io/autoupdate: "true"
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: cluster-admin
subjects:
- kind: ServiceAccount
name: admin-user
namespace: kube-system
#--------------------------admin.yaml--------------------------#
#执行安装
kubectl apply -f admin.yaml -n kube-system
登录dashboard
在谷歌浏览器（Chrome）启动文件中加入启动参数，用于解决无法访问Dashboard的问题，参考图1-1：
谷歌浏览器添加参数：
--test-type --ignore-certificate-errors
更改dashboard的svc为NodePort：
kubectl edit svc kubernetes-dashboard -n kubernetes-dashboard
spec:
clusterIP: 10.108.157.21
clusterIPs:
- 10.108.157.21
externalTrafficPolicy: Cluster
ports:
- nodePort: 30195
port: 443
protocol: TCP
targetPort: 8443
selector:
k8s-app: kubernetes-dashboard
sessionAffinity: None
type: ClusterIP #改为 NodePort
#修改完成后如下：
spec:
clusterIP: 10.108.157.21
clusterIPs:
- 10.108.157.21
externalTrafficPolicy: Cluster
ports:
- nodePort: 30195
port: 443
protocol: TCP
targetPort: 8443
selector:
k8s-app: kubernetes-dashboard
sessionAffinity: None
type: NodePort #已经改为NodePort
修改完成后访问dashboard：
#查看端口号：
kubectl get svc kubernetes-dashboard -n kubernetes-dashboard
7、通过https协议进行访问
https://192.168.3.31:30995/
#查看token值：
kubectl -n kube-system describe secret $(kubectl -n kube-system get secret | grep admin-user | awk '{print $1}')
#得到 token:
eyJhbGciOiJSUzI1NiIsImtpZCI6IlFkM3BUd0xxVEZ6a0t4Njl2QnVaMWhLNUl4NFlzUkVrQngzbmlQeG4zczgifQ.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJrdWJlLXN5c3RlbSIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VjcmV0Lm5hbWUiOiJhZG1pbi11c2VyLXRva2VuLXRidjRkIiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9zZXJ2aWNlLWFjY291bnQubmFtZSI6ImFkbWluLXVzZXIiLCJrdWJlcm5ldGVzLmlvL3NlcnZpY2VhY2NvdW50L3NlcnZpY2UtYWNjb3VudC51aWQiOiI0MzI2NDM1My1iNzY4LTRlNTEtYjljZS0wY2FlMzJlNThmOTgiLCJzdWIiOiJzeXN0ZW06c2VydmljZWFjY291bnQ6a3ViZS1zeXN0ZW06YWRtaW4tdXNlciJ9.jKtz39e-9EBlLhIW571Ms63ywad2z0s2hEa0ZalBRcEDXDKLN7jDejTLrrcyeNY5pRa8AUtbS1ckiYWI7OOlR3PBjD5Tgaz2HEKFw0FEoNMQnU8uLzR5WbUX4obOpzAyB4WYmCS9vK-ud98mmMHOT15Ee2BeaxIWTBL715m-NJcIxxByvsBtogVj7zWJayAVLOspMLps8hWk8XJDXpWEx0J8uU9KUPOey3YMiO5gNlk5TRHcZJOGg_7HV8_55MqKTQ8K9Jhsu5uVieB3kuJdwJdcGCGrMi1UVGx-RgJwGbZqMkXgy55QAp2he_sNFZmThhuxvz7FIclUyyoUZ43V9Q
将token粘贴到web页面上的token输入栏
8、 配置修改
将Kube-proxy改为ipvs模式，因为在初始化集群的时候注释了ipvs配置，所以需要自行修改一下：
在master01节点执行
kubectl edit cm kube-proxy -n kube-system
mode： 修改为 mode: ipvs
更新Kube-Proxy的Pod：
kubectl patch daemonset kube-proxy -p "{\"spec\":{\"template\":{\"metadata\":{\"annotations\":{\"date\":\"`date +'%s'`\"}}}}}" -n kube-system
验证Kube-Proxy模式：
curl 127.0.0.1:10249/proxyMode
ipvs
最后集群状态
root@k8s-master01[10:36:14]:~$ kubectl get nodes
NAME STATUS ROLES AGE VERSION
k8s-master01 Ready control-plane,master 19h v1.21.14
k8s-master02 Ready control-plane,master 19h v1.21.14
k8s-master03 Ready control-plane,master 19h v1.21.14
k8s-worker01 Ready <none> 19h v1.21.14
k8s-worker02 Ready <none> 19h v1.21.14
k8s-worker03 Ready <none> 19h v1.21.14
9、 高可用测试
k8s-master01是vip地址，停止eth0后vip消失，vip地址会漂移到k8s-master01上
10、 安装Kuboard集群管理面板
#在master01节点上执行
kubectl apply -f https://addons.kuboard.cn/kuboard/kuboard-v3.yaml
# 您也可以使用下面的指令，唯一的区别是，该指令使用华为云的镜像仓库替代 docker hub 分发 Kuboard 所需要的镜像
# kubectl apply -f https://addons.kuboard.cn/kuboard/kuboard-v3-swr.yaml
#执行指令 watch kubectl get pods -n kuboard，等待 kuboard 名称空间中所有的 Pod 就绪，如下所示，
Every 2.0s: kubectl get pods -n kuboard Thu Jan 18 14:20:40 2024
NAME READY STATUS RESTARTS AGE
kuboard-etcd-ltkjt 1/1 Running 0 3m54s
kuboard-etcd-m257r 0/1 ContainerCreating 0 3m54s
kuboard-etcd-q6dqw 1/1 Running 0 3m54s
kuboard-v3-5fc46b5557-qq6pk 0/1 ContainerCreating 0 3m53s
#最终完成后的状态
Every 2.0s: kubectl get pods -n kuboard Thu Jan 18 14:26:54 2024
NAME READY STATUS RESTARTS AGE
kuboard-agent-2-78b6856bb5-kw67d 1/1 Running 1 3m58s
kuboard-agent-857d7b8f45-dmctj 1/1 Running 1 3m58s
kuboard-etcd-ltkjt 1/1 Running 0 10m
kuboard-etcd-m257r 1/1 Running 0 10m
kuboard-etcd-q6dqw 1/1 Running 0 10m
kuboard-questdb-586fb449fc-hdvwp 1/1 Running 0 3m58s
kuboard-v3-5fc46b5557-qq6pk 1/1 Running 0 10m
访问 Kuboard
在浏览器中打开链接 http://your-node-ip-address:30080
输入初始用户名和密码，并登录
用户名： admin
密码： Kuboard123
浏览器兼容性
请使用 Chrome / FireFox / Safari / Edge 等浏览器
不兼容 IE 以及以 IE 为内核的浏览器
添加新的集群
Kuboard v3 是支持 Kubernetes 多集群管理的，在 Kuboard v3 的首页里，点击 添加集群 按钮，在向导的引导下可以完成集群的添加；
向 Kuboard v3 添加新的 Kubernetes 集群时，请确保：
您新添加集群可以访问到当前集群 Master 节点 内网IP 的 30080 TCP、30081 TCP、30081 UDP 端口；
如果您打算新添加到 Kuboard 中的集群与当前集群不在同一个局域网，请咨询 Kuboard 团队，帮助您解决问题。
根据提示添加集群，最后效果如下
评论区