• 【业务功能110】微服务-springcloud-springboot-Kubernetes集群部署-kubeadm极速部署-Docker安装

    kubeadm极速部署Kubernetes 1.24版本集群

    一、Kubernetes 1.24版本集群部署

    1.1 Kubernetes 1.24版本集群部署环境准备

    1.1.1 主机操作系统说明

    序号操作系统及版本备注
    1CentOS7u9

    1.1.2 主机硬件配置说明

    • 三台主机可以利用虚拟化VMware来部署

    1.准备Centos7 iso镜像
    2.VMware软件安装好一台虚拟机模板机，本地创建一个文件夹来存放虚拟机，按步骤执行即可，配置好所需要配置的虚拟机配置，时区，网段等
    3.虚拟机是由 配置文件 + 硬盘 组成， 那么我们接下来的三台虚拟机部署，就直接用前面的虚拟机模板中的硬盘，来创建(在前面指定的安装目录下 后缀是vmdk的就是磁盘文件)，因为系统都已经安装好在硬盘，所以利用模板去安装剩余的三台真实要使用的虚拟机，就很快了，减少重复的安装步骤
    4.分别创建三个文件夹，存放三个虚拟机，将前面模板机的vmdk磁盘文件都放到三个文件夹中，然后继续进行三次安装虚拟机操作，只是其中的 磁盘选项步骤，就是选择现有的对应目录下的模板机的磁盘。这样就可以快速安装好三台虚拟机了

    需求CPU内存硬盘角色主机名
    值4C8G100GBmasterk8s-master01
    值4C8G100GBworker(node)k8s-worker01
    值4C8G100GBworker(node)k8s-worker02

    1.1.3 主机配置

    1.1.3.1 主机名配置

    由于本次使用3台主机完成kubernetes集群部署，其中1台为master节点,名称为k8s-master01;其中2台为worker节点，名称分别为：k8s-worker01及k8s-worker02

    master节点
# hostnamectl set-hostname k8s-master01

    • 1
    • 2
    worker01节点
# hostnamectl set-hostname k8s-worker01

    • 1
    • 2
    worker02节点
# hostnamectl set-hostname k8s-worker02

    • 1
    • 2
    1.1.3.2 主机IP地址配置
    • vmware workstation虚拟机的gateway网关就是配置网络网段的第二个ip 比如192.168.10.2，C类地址网段，掩码24位，第二个ip
    • 119.29.29.29 腾讯的DNS服务
    • 配置好网络 重启后生效 systemctl restart network
    k8s-master节点IP地址为：192.168.10.141/24
# vim /etc/sysconfig/network-scripts/ifcfg-ens33
TYPE="Ethernet"
PROXY_METHOD="none"
BROWSER_ONLY="no"
BOOTPROTO="none"
DEFROUTE="yes"
IPV4_FAILURE_FATAL="no"
IPV6INIT="yes"
IPV6_AUTOCONF="yes"
IPV6_DEFROUTE="yes"
IPV6_FAILURE_FATAL="no"
IPV6_ADDR_GEN_MODE="stable-privacy"
NAME="ens33"
DEVICE="ens33"
ONBOOT="yes"
IPADDR="192.168.10.141"
PREFIX="24"
GATEWAY="192.168.10.2"
DNS1="119.29.29.29"

    • 1
    • 2
    • 3
    • 4
    • 5
    • 6
    • 7
    • 8
    • 9
    • 10
    • 11
    • 12
    • 13
    • 14
    • 15
    • 16
    • 17
    • 18
    • 19
    • 20
    k8s-worker1节点IP地址为：192.168.10.142/24
# vim /etc/sysconfig/network-scripts/ifcfg-ens33
TYPE="Ethernet"
PROXY_METHOD="none"
BROWSER_ONLY="no"
BOOTPROTO="none"
DEFROUTE="yes"
IPV4_FAILURE_FATAL="no"
IPV6INIT="yes"
IPV6_AUTOCONF="yes"
IPV6_DEFROUTE="yes"
IPV6_FAILURE_FATAL="no"
IPV6_ADDR_GEN_MODE="stable-privacy"
NAME="ens33"
DEVICE="ens33"
ONBOOT="yes"
IPADDR="192.168.10.142"
PREFIX="24"
GATEWAY="192.168.10.2"
DNS1="119.29.29.29"

    • 1
    • 2
    • 3
    • 4
    • 5
    • 6
    • 7
    • 8
    • 9
    • 10
    • 11
    • 12
    • 13
    • 14
    • 15
    • 16
    • 17
    • 18
    • 19
    • 20
    k8s-worker2节点IP地址为：192.168.10.143/24
# vim /etc/sysconfig/network-scripts/ifcfg-ens33
TYPE="Ethernet"
PROXY_METHOD="none"
BROWSER_ONLY="no"
BOOTPROTO="none"
DEFROUTE="yes"
IPV4_FAILURE_FATAL="no"
IPV6INIT="yes"
IPV6_AUTOCONF="yes"
IPV6_DEFROUTE="yes"
IPV6_FAILURE_FATAL="no"
IPV6_ADDR_GEN_MODE="stable-privacy"
NAME="ens33"
DEVICE="ens33"
ONBOOT="yes"
IPADDR="192.168.10.143"
PREFIX="24"
GATEWAY="192.168.10.2"
DNS1="119.29.29.29"


    • 1
    • 2
    • 3
    • 4
    • 5
    • 6
    • 7
    • 8
    • 9
    • 10
    • 11
    • 12
    • 13
    • 14
    • 15
    • 16
    • 17
    • 18
    • 19
    • 20
    • 21
    1.1.3.3 主机名与IP地址解析

    所有集群主机均需要进行配置。

    # cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.10.141 k8s-master01
192.168.10.142 k8s-worker01
192.168.10.143 k8s-worker02

    • 1
    • 2
    • 3
    • 4
    • 5
    • 6
    1.1.3.4 防火墙配置

    所有主机均需要操作。

    关闭现有防火墙firewalld
# systemctl disable firewalld
# systemctl stop firewalld
# firewall-cmd --state
not running

    • 1
    • 2
    • 3
    • 4
    • 5
    1.1.3.5 SELINUX配置

    所有主机均需要操作。修改SELinux配置需要重启操作系统。 SELINUX=disabled

    # sed -ri 's/SELINUX=enforcing/SELINUX=disabled/' /etc/selinux/config

    • 1
    1.1.3.6 时间同步配置

    所有主机均需要操作。最小化安装系统需要安装ntpdate软件。

    # crontab -l
0 */1 * * * /usr/sbin/ntpdate time1.aliyun.com

    • 1
    • 2
    1.1.3.7 升级操作系统内核

    所有主机均需要操作。

    导入elrepo gpg key
# rpm --import https://www.elrepo.org/RPM-GPG-KEY-elrepo.org

    • 1
    • 2
    安装elrepo YUM源仓库
# yum -y install https://www.elrepo.org/elrepo-release-7.0-4.el7.elrepo.noarch.rpm

    • 1
    • 2
    安装kernel-ml版本，ml为长期稳定版本，lt为长期维护版本
# yum --enablerepo="elrepo-kernel" -y install kernel-lt.x86_64

    • 1
    • 2
    设置grub2默认引导为0
# grub2-set-default 0

    • 1
    • 2
    重新生成grub2引导文件
# grub2-mkconfig -o /boot/grub2/grub.cfg

    • 1
    • 2
    更新后，需要重启，使用升级的内核生效。
# reboot

    • 1
    • 2
    重启后，需要验证内核是否为更新对应的版本
# uname -r

    • 1
    • 2
    1.1.3.8 配置内核转发及网桥过滤

    所有主机均需要操作。

    添加网桥过滤及内核转发配置文件
# cat /etc/sysctl.d/k8s.conf
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1
net.ipv4.ip_forward = 1
vm.swappiness = 0

    • 1
    • 2
    • 3
    • 4
    • 5
    • 6
    加载br_netfilter模块
# modprobe br_netfilter

    • 1
    • 2
    查看是否加载
# lsmod | grep br_netfilter
br_netfilter           22256  0
bridge                151336  1 br_netfilter

    • 1
    • 2
    • 3
    • 4
    1.1.3.9 安装ipset及ipvsadm

    所有主机均需要操作。 汇总路由，查询方便

    安装ipset及ipvsadm
# yum -y install ipset ipvsadm

    • 1
    • 2
    配置ipvsadm模块加载方式
添加需要加载的模块
# cat > /etc/sysconfig/modules/ipvs.modules <
#!/bin/bash
modprobe -- ip_vs
modprobe -- ip_vs_rr
modprobe -- ip_vs_wrr
modprobe -- ip_vs_sh
modprobe -- nf_conntrack
EOF

    • 1
    • 2
    • 3
    • 4
    • 5
    • 6
    • 7
    • 8
    • 9
    • 10
    授权、运行、检查是否加载
# chmod 755 /etc/sysconfig/modules/ipvs.modules && bash /etc/sysconfig/modules/ipvs.modules && lsmod | grep -e ip_vs -e nf_conntrack

    • 1
    • 2
    1.1.3.10 关闭SWAP分区
    • 开启的话会影响性能，速度 比较慢

    修改完成后需要重启操作系统，如不重启，可临时关闭，命令为swapoff -a

    永远关闭swap分区，需要重启操作系统
# cat /etc/fstab
......

# /dev/mapper/centos-swap swap                    swap    defaults        0 0

在上一行中行首添加#

    • 1
    • 2
    • 3
    • 4
    • 5
    • 6
    • 7

    1.2 Docker准备

    1.2.1 Docker安装YUM源准备

    使用阿里云开源软件镜像站。 -O 下载的文件指定放到具体的目录位置

    # wget https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo -O /etc/yum.repos.d/docker-ce.repo

    • 1

    1.2.2 Docker安装

    # yum -y install docker-ce

    • 1

    1.2.3 启动Docker服务

    # systemctl enable --now docker

    • 1

    1.2.4 修改cgroup方式

    /etc/docker/daemon.json 默认没有此文件，需要单独创建

    在/etc/docker/daemon.json添加如下内容

# cat /etc/docker/daemon.json
{
        "exec-opts": ["native.cgroupdriver=systemd"]
}

    • 1
    • 2
    • 3
    • 4
    • 5
    • 6
    • 重启docker ， 通过info命令查看是否修改完成 ： 打印出来信息 Cgroup Driver: systemd
    # systemctl restart docker
# docker info    

    • 1
    • 2

    1.2.5 cri-dockerd安装

    1.2.5.1 golang环境准备
    wget https://storage.googleapis.com/golang/getgo/installer_linux

chmod +x ./installer_linux

./installer_linux

source ~/.bash_profile

    • 1
    • 2
    • 3
    • 4
    • 5
    • 6
    • 7
    2.2.5.2 构建并安装cri-dockerd
    • 登录github 查询 Mirantis/cri-dockerd 克隆源码到 每一台主机都需要操作 然后根据项目的readme.md查看具体的安装命令步骤，如下
    克隆cri-dockerd源码
# git clone https://github.com/Mirantis/cri-dockerd.git

    • 1
    • 2
    查看克隆下来的目录
# ls
cri-dockerd 

    • 1
    • 2
    • 3
    查看目录中内容
# ls cri-dockerd/
LICENSE  Makefile  packaging  README.md  src  VERSION

    • 1
    • 2
    • 3
    # cd cri-dockerd

    • 1
    创建bin目录并构建cri-dockerd二进制文件
# mkdir bin
# go get && go build -o ../bin/cri-dockerd

    • 1
    • 2
    • 3
    创建/usr/local/bin,默认存在时，可不用创建
# mkdir -p /usr/local/bin

安装cri-dockerd
# install -o root -g root -m 0755 bin/cri-dockerd /usr/local/bin/cri-dockerd

复制服务管理文件至/etc/systemd/system目录中
# cp -a packaging/systemd/* /etc/systemd/system

指定cri-dockerd运行位置
#sed -i -e 's,/usr/bin/cri-dockerd,/usr/local/bin/cri-dockerd,' /etc/systemd/system/cri-docker.service

启动服务
# systemctl daemon-reload
# systemctl enable cri-docker.service
# systemctl enable --now cri-docker.socket

    • 1
    • 2
    • 3
    • 4
    • 5
    • 6
    • 7
    • 8
    • 9
    • 10
    • 11
    • 12
    • 13
    • 14
    • 15
    • 16

    1.3 kubernetes 1.24.X 集群部署

    1.3.1 集群软件及版本说明

    kubeadmkubeletkubectl
    版本1.24.X1.24.X1.24.X
    安装位置集群所有主机集群所有主机集群所有主机
    作用初始化集群、管理集群等用于接收api-server指令，对pod生命周期进行管理集群应用命令行管理工具

    1.3.2 kubernetes YUM源准备

    1.3.2.1 谷歌YUM源
    [kubernetes]
name=Kubernetes
baseurl=https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64
enabled=1
gpgcheck=0
repo_gpgcheck=0
gpgkey=https://packages.cloud.google.com/yum/doc/yum-key.gpg
        https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg

    • 1
    • 2
    • 3
    • 4
    • 5
    • 6
    • 7
    • 8
    1.3.2.2 阿里云YUM源
    [kubernetes]
name=Kubernetes
baseurl=https://mirrors.aliyun.com/kubernetes/yum/repos/kubernetes-el7-x86_64/
enabled=1
gpgcheck=0
repo_gpgcheck=0
gpgkey=https://mirrors.aliyun.com/kubernetes/yum/doc/yum-key.gpg https://mirrors.aliyun.com/kubernetes/yum/doc/rpm-package-key.gpg

    • 1
    • 2
    • 3
    • 4
    • 5
    • 6
    • 7

    1.3.3 集群软件安装

    所有节点均可安装

    默认安装
# yum -y install  kubeadm  kubelet kubectl

    • 1
    • 2
    查看指定版本
# yum list kubeadm.x86_64 --showduplicates | sort -r
# yum list kubelet.x86_64 --showduplicates | sort -r
# yum list kubectl.x86_64 --showduplicates | sort -r

    • 1
    • 2
    • 3
    • 4
    安装指定版本
# yum -y install  kubeadm-1.24.7-0  kubelet-1.24.7-0 kubectl-1.24.7-0

    • 1
    • 2

    1.3.4 配置kubelet

    为了实现docker使用的cgroupdriver与kubelet使用的cgroup的一致性，建议修改如下文件内容。

    # vim /etc/sysconfig/kubelet
KUBELET_EXTRA_ARGS="--cgroup-driver=systemd"

    • 1
    • 2
    设置kubelet为开机自启动即可，由于没有生成配置文件，集群初始化后自动启动
# systemctl enable kubelet

    • 1
    • 2

    1.3.5 集群镜像准备 只需在master节点主机执行

    可使用VPN实现下载。
    查看镜像列表，然后将打印出来的镜像列表都下载下来
    由于镜像列表较多，可以编写一个脚本文件，循环去通过docker拉取镜像来完成批量的镜像下载

    # kubeadm config images list --kubernetes-version=v1.24.7

    • 1
    # cat image_download.sh
#!/bin/bash
images_list='
镜像列表'

for i in $images_list
do
        docker pull $i
done

docker save -o k8s-1-24-X.tar $images_list

    • 1
    • 2
    • 3
    • 4
    • 5
    • 6
    • 7
    • 8
    • 9
    • 10
    • 11
    • 通过 sh image_download.sh 来执行脚本 完成镜像下载
    • 脚本中的docker save -o k8s-1-24-X.tar $images_list 是打包成jar包方便去执行

    1.3.6 集群初始化 只需在master节点主机执行

    [root@k8s-master01 ~]# kubeadm init --kubernetes-version=v1.24.7 --pod-network-cidr=10.224.0.0/16 --apiserver-advertise-address=192.168.10.141  --cri-socket unix:///var/run/cri-dockerd.sock

    • 1
    如果不添加--cri-socket选项，则会报错，内容如下：
Found multiple CRI endpoints on the host. Please define which one do you wish to use by setting the 'criSocket' field in the kubeadm configuration file: unix:///var/run/containerd/containerd.sock, unix:///var/run/cri-dockerd.sock
To see the stack trace of this error execute with --v=5 or higher

    • 1
    • 2
    • 3
    初始化过程输出
[init] Using Kubernetes version: v1.24.0
[preflight] Running pre-flight checks
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
[certs] Using certificateDir folder "/etc/kubernetes/pki"
[certs] Generating "ca" certificate and key
[certs] Generating "apiserver" certificate and key
[certs] apiserver serving cert is signed for DNS names [k8s-master01 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 192.168.10.200]
[certs] Generating "apiserver-kubelet-client" certificate and key
[certs] Generating "front-proxy-ca" certificate and key
[certs] Generating "front-proxy-client" certificate and key
[certs] Generating "etcd/ca" certificate and key
[certs] Generating "etcd/server" certificate and key
[certs] etcd/server serving cert is signed for DNS names [k8s-master01 localhost] and IPs [192.168.10.200 127.0.0.1 ::1]
[certs] Generating "etcd/peer" certificate and key
[certs] etcd/peer serving cert is signed for DNS names [k8s-master01 localhost] and IPs [192.168.10.200 127.0.0.1 ::1]
[certs] Generating "etcd/healthcheck-client" certificate and key
[certs] Generating "apiserver-etcd-client" certificate and key
[certs] Generating "sa" key and public key
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[kubeconfig] Writing "admin.conf" kubeconfig file
[kubeconfig] Writing "kubelet.conf" kubeconfig file
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
[kubeconfig] Writing "scheduler.conf" kubeconfig file
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Starting the kubelet
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
[control-plane] Creating static Pod manifest for "kube-scheduler"
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[apiclient] All control plane components are healthy after 13.006785 seconds
[upload-config] Storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace
[kubelet] Creating a ConfigMap "kubelet-config" in namespace kube-system with the configuration for the kubelets in the cluster
[upload-certs] Skipping phase. Please see --upload-certs
[mark-control-plane] Marking the node k8s-master01 as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-load-balancers]
[mark-control-plane] Marking the node k8s-master01 as control-plane by adding the taints [node-role.kubernetes.io/master:NoSchedule node-role.kubernetes.io/control-plane:NoSchedule]
[bootstrap-token] Using token: 8x4o2u.hslo8xzwwlrncr8s
[bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles
[bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes
[bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials
[bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token
[bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster
[bootstrap-token] Creating the "cluster-info" ConfigMap in the "kube-public" namespace
[kubelet-finalize] Updating "/etc/kubernetes/kubelet.conf" to point to a rotatable kubelet client certificate and key
[addons] Applied essential addon: CoreDNS
[addons] Applied essential addon: kube-proxy

Your Kubernetes control-plane has initialized successfully!

To start using your cluster, you need to run the following as a regular user:

  mkdir -p $HOME/.kube
  sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
  sudo chown $(id -u):$(id -g) $HOME/.kube/config

Alternatively, if you are the root user, you can run:

  export KUBECONFIG=/etc/kubernetes/admin.conf

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/

Then you can join any number of worker nodes by running the following on each as root:

kubeadm join 192.168.10.200:6443 --token 8x4o2u.hslo8xzwwlrncr8s \
        --discovery-token-ca-cert-hash sha256:7323a8b0658fc33d89e627f078f6eb16ac94394f9a91b3335dd3ce73a3f313a0

    • 1
    • 2
    • 3
    • 4
    • 5
    • 6
    • 7
    • 8
    • 9
    • 10
    • 11
    • 12
    • 13
    • 14
    • 15
    • 16
    • 17
    • 18
    • 19
    • 20
    • 21
    • 22
    • 23
    • 24
    • 25
    • 26
    • 27
    • 28
    • 29
    • 30
    • 31
    • 32
    • 33
    • 34
    • 35
    • 36
    • 37
    • 38
    • 39
    • 40
    • 41
    • 42
    • 43
    • 44
    • 45
    • 46
    • 47
    • 48
    • 49
    • 50
    • 51
    • 52
    • 53
    • 54
    • 55
    • 56
    • 57
    • 58
    • 59
    • 60
    • 61
    • 62
    • 63
    • 64
    • 65
    • 66
    • 67
    • 68
    • 69
    • 70
    • 71
    • 72

    1.3.7 集群应用客户端管理集群文件准备

    [root@k8s-master01 ~]# mkdir -p $HOME/.kube
[root@k8s-master01 ~]# cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
[root@k8s-master01 ~]# chown $(id -u):$(id -g) $HOME/.kube/config
[root@k8s-master01 ~]# ls /root/.kube/config

//查看节点状态是否成功,显示状态ready 即可
kubectl get nodess

    • 1
    • 2
    • 3
    • 4
    • 5
    • 6
    • 7
    [root@k8s-master01 ~]# export KUBECONFIG=/etc/kubernetes/admin.conf

    • 1

    1.3.8 集群网络准备

    使用calico部署集群网络

    安装参考网址：https://projectcalico.docs.tigera.io/about/about-calico

    1.3.8.1 calico安装 网络配置
    • 方式一（不推荐）
    下载operator资源清单文件
[root@k8s-master01 ~]# wget https://docs.projectcalico.org/manifests/tigera-operator.yaml

    • 1
    • 2
    应用资源清单文件，创建operator
[root@k8s-master01 ~]# kubectl create -f tigera-operator.yaml

    • 1
    • 2
    • 方式二（推荐自定义）
    通过自定义资源方式安装
[root@k8s-master01 ~]# wget https://docs.projectcalico.org/manifests/custom-resources.yaml

    • 1
    • 2

    网络配置,修改网段，前面在集群主节点master初始化的 网络节点地址段才能找到pod-network-cidr=10.224.0.0/16

    修改文件第13行，修改为使用kubeadm init ----pod-network-cidr对应的IP地址段
[root@k8s-master01 ~]# vim custom-resources.yaml
......
 11     ipPools:
 12     - blockSize: 26
 13       cidr: 10.224.0.0/16 
 14       encapsulation: VXLANCrossSubnet
......

    • 1
    • 2
    • 3
    • 4
    • 5
    • 6
    • 7
    • 8
      //当node无法正常运行时，可考虑在此文件中添加相关内容。   与ipPools同级的参数 注意位置 
  // ens.* 是网卡的名称匹配 系统默认网卡的名称是ens开头的，具体看系统网卡名称
      nodeAddressAutodetectionV4:
        interface: ens.*

    • 1
    • 2
    • 3
    • 4
    应用资源清单文件
[root@k8s-master01 ~]# kubectl apply -f custom-resources.yaml

    • 1
    • 2
    监视calico-sysem命名空间中pod运行情况
[root@k8s-master01 ~]# watch kubectl get pods -n calico-system

    • 1
    • 2

    Wait until each pod has the STATUS of Running.

    删除 master 上的 taint
[root@k8s-master01 ~]# kubectl taint nodes --all node-role.kubernetes.io/master-

    • 1
    • 2
    已经全部运行   查看所有节点命令： kubectl get nodes   
[root@k8s-master01 ~]# kubectl get pods -n calico-system
NAME                                      READY   STATUS    RESTARTS   AGE
calico-kube-controllers-666bb9949-dzp68   1/1     Running   0          11m
calico-node-jhcf4                         1/1     Running   4          11m
calico-typha-68b96d8d9c-7qfq7             1/1     Running   2          11m

    • 1
    • 2
    • 3
    • 4
    • 5
    • 6
    查看kube-system命名空间中coredns状态，处于Running状态表明联网成功。
[root@k8s-master01 ~]# kubectl get pods -n kube-system
NAME                                   READY   STATUS    RESTARTS   AGE
coredns-6d4b75cb6d-js5pl               1/1     Running   0          12h
coredns-6d4b75cb6d-zm8pc               1/1     Running   0          12h
etcd-k8s-master01                      1/1     Running   0          12h
kube-apiserver-k8s-master01            1/1     Running   0          12h
kube-controller-manager-k8s-master01   1/1     Running   0          12h
kube-proxy-7nhr7                       1/1     Running   0          12h
kube-proxy-fv4kr                       1/1     Running   0          12h
kube-proxy-vv5vg                       1/1     Running   0          12h
kube-scheduler-k8s-master01            1/1     Running   0          12h

    • 1
    • 2
    • 3
    • 4
    • 5
    • 6
    • 7
    • 8
    • 9
    • 10
    • 11
    • 12
    2.3.8.2 calico客户端安装
    下载二进制文件
# curl -L https://github.com/projectcalico/calico/releases/download/v3.21.4/calicoctl-linux-amd64 -o calicoctl


    • 1
    • 2
    • 3
    安装calicoctl
# mv calicoctl /usr/bin/

为calicoctl添加可执行权限
# chmod +x /usr/bin/calicoctl

查看添加权限后文件
# ls /usr/bin/calicoctl
/usr/bin/calicoctl

查看calicoctl版本
# calicoctl  version
Client Version:    v3.21.4
Git commit:        220d04c94
Cluster Version:   v3.21.4
Cluster Type:      typha,kdd,k8s,operator,bgp,kubeadm

    • 1
    • 2
    • 3
    • 4
    • 5
    • 6
    • 7
    • 8
    • 9
    • 10
    • 11
    • 12
    • 13
    • 14
    • 15
    • 16
    通过~/.kube/config连接kubernetes集群，查看已运行节点
# DATASTORE_TYPE=kubernetes KUBECONFIG=~/.kube/config calicoctl get nodes
NAME
k8s-master01

    • 1
    • 2
    • 3
    • 4

    1.3.9 集群工作节点添加

    因容器镜像下载较慢，可能会导致报错，主要错误为没有准备好cni（集群网络插件），如有网络，请耐心等待即可。

    • 进入到两台worker节点主机进行命令执行
    [root@k8s-worker01 ~]# kubeadm join 192.168.10.200:6443 --token 8x4o2u.hslo8xzwwlrncr8s \                              --discovery-token-ca-cert-hash sha256:7323a8b0658fc33d89e627f078f6eb16ac94394f9a91b3335dd3ce73a3f313a0 --cri-socket unix:///var/run/cri-dockerd.sock

    • 1
    [root@k8s-worker02 ~]# kubeadm join 192.168.10.200:6443 --token 8x4o2u.hslo8xzwwlrncr8s \
        --discovery-token-ca-cert-hash sha256:7323a8b0658fc33d89e627f078f6eb16ac94394f9a91b3335dd3ce73a3f313a0 --cri-socket unix:///var/run/cri-dockerd.sock

    • 1
    • 2
    在master节点上操作，查看网络节点是否添加： kubectl get nodes
# DATASTORE_TYPE=kubernetes KUBECONFIG=~/.kube/config calicoctl get nodes
NAME
k8s-master01
k8s-worker01
k8s-worker02

    • 1
    • 2
    • 3
    • 4
    • 5
    • 6

    二、 验证集群可用性

    查看所有的节点
[root@k8s-master01 ~]# kubectl get nodes
NAME           STATUS   ROLES           AGE   VERSION
k8s-master01   Ready    control-plane   12h   v1.24.0
k8s-worker01   Ready              12h   v1.24.0
k8s-worker02   Ready              12h   v1.24.0

    • 1
    • 2
    • 3
    • 4
    • 5
    • 6
    查看集群健康情况
[root@k8s-master01 ~]# kubectl get cs
Warning: v1 ComponentStatus is deprecated in v1.19+
NAME                 STATUS    MESSAGE                         ERROR
controller-manager   Healthy   ok
scheduler            Healthy   ok
etcd-0               Healthy   {"health":"true","reason":""}

    • 1
    • 2
    • 3
    • 4
    • 5
    • 6
    • 7
    查看kubernetes集群pod运行情况
[root@k8s-master01 ~]# kubectl get pods -n kube-system
NAME                                   READY   STATUS    RESTARTS   AGE
coredns-6d4b75cb6d-js5pl               1/1     Running   0          12h
coredns-6d4b75cb6d-zm8pc               1/1     Running   0          12h
etcd-k8s-master01                      1/1     Running   0          12h
kube-apiserver-k8s-master01            1/1     Running   0          12h
kube-controller-manager-k8s-master01   1/1     Running   0          12h
kube-proxy-7nhr7                       1/1     Running   0          12h
kube-proxy-fv4kr                       1/1     Running   0          12h
kube-proxy-vv5vg                       1/1     Running   0          12h
kube-scheduler-k8s-master01            1/1     Running   0          12h

    • 1
    • 2
    • 3
    • 4
    • 5
    • 6
    • 7
    • 8
    • 9
    • 10
    • 11
    • 12
    再次查看calico-system命名空间中pod运行情况。
[root@k8s-master01 ~]# kubectl get pods -n calico-system
NAME                                       READY   STATUS    RESTARTS   AGE
calico-kube-controllers-5b544d9b48-xgfnk   1/1     Running   0          12h
calico-node-7clf4                          1/1     Running   0          12h
calico-node-cjwns                          1/1     Running   0          12h
calico-node-hhr4n                          1/1     Running   0          12h
calico-typha-6cb6976b97-5lnpk              1/1     Running   0          12h
calico-typha-6cb6976b97-9w9s8              1/1     Running   0          12h

    • 1
    • 2
    • 3
    • 4
    • 5
    • 6
    • 7
    • 8
    • 9
  • 相关阅读:
    Boost.Interprocess 的同步
    Selenium+Python系列（二） - 元素定位那些事
    MySQL JDBC编程
    在SSL中进行交叉熵学习的步骤
    react中受控组件与非受控组件
    Alexa智能家居构建技能教程(官网版翻译=保姆级)
    Shiro
    如何在Windows下创建Ramdisk
    加解密和加签验签
    SpringBoot关闭Tomcat容器，SpringBoot使用Jetty容器
  • 原文地址：https://blog.csdn.net/studyday1/article/details/132864359