您当前的位置： 首页 > 慢生活 > 程序人生 网站首页程序人生
66、Kubernetes - 高可用的 K8S 构建（1）_]
发布时间：2023-02-05 20:35:58编辑：雪饮阅读（）
192.168.66.10，192.168.66.20，192.168.66.21都执行的操作
kubeadm reset
确保防火墙状态为inactive (dead)
systemctl status firewalld
确保iptables为激活状态active (exited)
systemctl status iptables
确保selinux为关闭状态Disabled
getenforce
主机名配置
然后几台主机名分别设置为
192.168.66.10 k8s-master01
192.168.66.20 k8s-master02
192.168.66.21 k8s-master03
192.168.66.100 k8s-vip
[root@k8s-master01 ~]# hostnamectl set-hostname k8s-master01
[root@k8s-master01 ~]# hostname
hostname
k8s-master01
[root@k8s-node01 ~]# hostnamectl set-hostname k8s-master02
[root@k8s-node01 ~]# hostname
k8s-master02
[root@k8s-node02 ~]# hostnamectl set-hostname k8s-master03
[root@k8s-node02 ~]# hostname
k8s-master03
[root@k8s-master01 ~]# cat /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.66.100 hub.atguigu.com
192.168.66.10 k8s-master01
192.168.66.20 k8s-master02
192.168.66.21 k8s-master03
192.168.66.100 k8s-vip
[root@k8s-node01 ~]# cat /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.66.100 hub.atguigu.com
192.168.66.10 k8s-master01
192.168.66.20 k8s-master02
192.168.66.21 k8s-master03
192.168.66.100 k8s-vip
[root@k8s-node02 ~]# cat /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.66.100 hub.atguigu.com
192.168.66.10 k8s-master01
192.168.66.20 k8s-master02
192.168.66.21 k8s-master03
192.168.66.100 k8s-vip
[root@hub ~]# cat /etc/hosts
cat /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.66.100 hub.atguigu.com
192.168.66.10 k8s-master01
192.168.66.20 k8s-master02
192.168.66.21 k8s-master03
192.168.66.100 k8s-vip
接下来就是主机名配置的结果校验
[root@k8s-master01 ~]# ping -c 4 k8s-master01 && ping -c 4 k8s-master02 && ping -c 4 k8s-master03 && ping -c 4 k8s-vip
PING k8s-master01 (192.168.66.10) 56(84) bytes of data.
64 bytes from k8s-master01 (192.168.66.10): icmp_seq=1 ttl=64 time=0.031 ms
64 bytes from k8s-master01 (192.168.66.10): icmp_seq=2 ttl=64 time=0.034 ms
64 bytes from k8s-master01 (192.168.66.10): icmp_seq=3 ttl=64 time=0.033 ms
64 bytes from k8s-master01 (192.168.66.10): icmp_seq=4 ttl=64 time=0.076 ms
--- k8s-master01 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3071ms
rtt min/avg/max/mdev = 0.031/0.043/0.076/0.019 ms
PING k8s-master02 (192.168.66.20) 56(84) bytes of data.
64 bytes from k8s-master02 (192.168.66.20): icmp_seq=1 ttl=64 time=0.502 ms
64 bytes from k8s-master02 (192.168.66.20): icmp_seq=2 ttl=64 time=0.723 ms
64 bytes from k8s-master02 (192.168.66.20): icmp_seq=3 ttl=64 time=1.52 ms
64 bytes from k8s-master02 (192.168.66.20): icmp_seq=4 ttl=64 time=1.48 ms
--- k8s-master02 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3052ms
rtt min/avg/max/mdev = 0.502/1.059/1.526/0.455 ms
PING k8s-master03 (192.168.66.21) 56(84) bytes of data.
64 bytes from k8s-master03 (192.168.66.21): icmp_seq=1 ttl=64 time=0.428 ms
64 bytes from k8s-master03 (192.168.66.21): icmp_seq=2 ttl=64 time=1.51 ms
64 bytes from k8s-master03 (192.168.66.21): icmp_seq=3 ttl=64 time=1.20 ms
64 bytes from k8s-master03 (192.168.66.21): icmp_seq=4 ttl=64 time=0.969 ms
--- k8s-master03 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3041ms
rtt min/avg/max/mdev = 0.428/1.029/1.514/0.397 ms
PING k8s-vip (192.168.66.100) 56(84) bytes of data.
64 bytes from hub.atguigu.com (192.168.66.100): icmp_seq=1 ttl=64 time=0.277 ms
64 bytes from hub.atguigu.com (192.168.66.100): icmp_seq=2 ttl=64 time=0.435 ms
64 bytes from hub.atguigu.com (192.168.66.100): icmp_seq=3 ttl=64 time=0.404 ms
64 bytes from hub.atguigu.com (192.168.66.100): icmp_seq=4 ttl=64 time=0.753 ms
--- k8s-vip ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3107ms
rtt min/avg/max/mdev = 0.277/0.467/0.753/0.175 ms
这项测试在上面4个节点都测试下
[root@k8s-node01 ~]# ping -c 4 k8s-master01 && ping -c 4 k8s-master02 && ping -c 4 k8s-master03 && ping -c 4 k8s-vip
[root@k8s-node02 ~]# ping -c 4 k8s-master01 && ping -c 4 k8s-master02 && ping -c 4 k8s-master03 && ping -c 4 k8s-vip
[root@hub ~]# ping -c 4 k8s-master01 && ping -c 4 k8s-master02 && ping -c 4 k8s-master03 && ping -c 4 k8s-vip
依赖安装
上面四个节点都安装
yum install -y conntrack ntpdate ntp ipvsadm ipset jq iptables curl sysstat libseccomp wget vim net-tools git
并且这四个节点都关闭swap（vip节点可能不需要，但是我还是执行下，应该没有什么事情吧）（但我看老师vip节点是没有执行的，并且老师vip节点主机名好像也没有设置）
swapoff -a && sed -i '/ swap / s/^\(.*\)$/#\1/g' /etc/fstab
三个master都初始化内核脚本
cat > kubernetes.conf <<EOF
net.bridge.bridge-nf-call-iptables=1
net.bridge.bridge-nf-call-ip6tables=1
net.ipv4.ip_forward=1
net.ipv4.tcp_tw_recycle=0
vm.swappiness=0
vm.overcommit_memory=1
vm.panic_on_oom=0
fs.inotify.max_user_instances=8192
fs.inotify.max_user_watches=1048576
fs.file-max=52706963
fs.nr_open=52706963
net.ipv6.conf.all.disable_ipv6=1
net.netfilter.nf_conntrack_max=2310720
EOF
最后
关于之前的那个kibana状态问题，则可以尝试从下面这几个方面再次尝试下
systemctl status firewalld
确保iptables为激活状态active (exited)
systemctl status iptables
确保selinux为关闭状态Disabled
getenforce
以及上面初始化脚本时候的
vm.overcommit_memory=1
内核初始化里面的注释也检查下，如有注释就都清理掉注释。
关键字词：Kubernetes,高可用,K8S,构建