一、準(zhǔn)備環(huán)境

1.1 Kubernetes 1.27.3 版本集群部署環(huán)境準(zhǔn)備

1.1.1?主機(jī)硬件配置說(shuō)明

1.1.2?主機(jī)配置

1.1.2.1 主機(jī)名配置

由于本次使用3臺(tái)主機(jī)完成kubernetes集群部署，其中1臺(tái)為master節(jié)點(diǎn),名稱為master01;其中2臺(tái)為worker節(jié)點(diǎn)，名稱分別為：worker01，worker02

master節(jié)點(diǎn)
# hostnamectl set-hostname master01

worker01節(jié)點(diǎn)
# hostnamectl set-hostname worker01

worker02節(jié)點(diǎn)
# hostnamectl set-hostname worker02

1.1.2.2 主機(jī)IP地址配置

1.1.2.3 主機(jī)名與IP地址解析

所有集群主機(jī)均需要進(jìn)行配置

# cat /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.1.110 master01
192.168.1.111 worker01
192.168.1.112 worker02

1.1.2.4 防火墻配置

所有主機(jī)均需要操作。

關(guān)閉現(xiàn)有防火墻firewalld
# systemctl disable firewalld
# systemctl stop firewalld
# firewall-cmd --state
not running

1.1.2.5 SELINUX配置

所有主機(jī)均需要操作。修改SELinux配置需要重啟操作系統(tǒng)。

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

1.1.2.6 時(shí)間同步配置

所有主機(jī)均需要操作。最小化安裝系統(tǒng)需要安裝ntpdate軟件。

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

1.1.2.7 升級(jí)操作系統(tǒng)內(nèi)核

所有主機(jī)均需要操作。

導(dǎo)入elrepo gpg key
# rpm --import https://www.elrepo.org/RPM-GPG-KEY-elrepo.org

安裝elrepo YUM源倉(cāng)庫(kù)
# yum -y install https://www.elrepo.org/elrepo-release-7.0-4.el7.elrepo.noarch.rpm

安裝kernel-ml版本，ml為長(zhǎng)期穩(wěn)定版本，lt為長(zhǎng)期維護(hù)版本
# yum --enablerepo="elrepo-kernel" -y install kernel-lt.x86_64

設(shè)置grub2默認(rèn)引導(dǎo)為0
# grub2-set-default 0

重新生成grub2引導(dǎo)文件
# grub2-mkconfig -o /boot/grub2/grub.cfg

更新后，需要重啟，使用升級(jí)的內(nèi)核生效。

# reboot

重啟后，需要驗(yàn)證內(nèi)核是否為更新對(duì)應(yīng)的版本
# uname -r

1.1.2.8 配置內(nèi)核轉(zhuǎn)發(fā)及網(wǎng)橋過(guò)濾

所有主機(jī)均需要操作。

添加網(wǎng)橋過(guò)濾及內(nèi)核轉(zhuǎn)發(fā)配置文件
# cat > /etc/sysctl.d/k8s.conf << EOF
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1
net.ipv4.ip_forward = 1
vm.swappiness = 0
EOF

加載br_netfilter模塊
# modprobe br_netfilter

查看是否加載
# lsmod | grep br_netfilter
br_netfilter ? ? ? ? ? 22256 ?0
bridge ? ? ? ? ? ? ? ?151336 ?1 br_netfilter

1.1.2.9 安裝ipset及ipvsadm

所有主機(jī)均需要操作。

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

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

授權(quán)、運(yùn)行、檢查是否加載
# chmod 755 /etc/sysconfig/modules/ipvs.modules && bash /etc/sysconfig/modules/ipvs.modules && lsmod | grep -e ip_vs -e nf_conntrack

1.1.2.10 關(guān)閉SWAP分區(qū)

修改完成后需要重啟操作系統(tǒng)，如不重啟，可臨時(shí)關(guān)閉，命令為swapoff -a

永遠(yuǎn)關(guān)閉swap分區(qū)，需要重啟操作系統(tǒng)
# cat /etc/fstab
......

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

在上一行中行首添加#

二、容器運(yùn)行時(shí) Containerd準(zhǔn)備

2.1 Containerd準(zhǔn)備

2.1.1 Containerd部署文件獲取

# wget https://github.com/containerd/containerd/releases/download/v1.7.0/cri-containerd-cni-1.7.0-linux-amd64.tar.gz

# tar xf cri-containerd-cni-1.7.0-linux-amd64.tar.gz -C /

2.1.2 Containerd配置文件生成并修改

# mkdir /etc/containerd

# containerd config default > /etc/containerd/config.toml

# vim /etc/containerd/config.toml

sandbox_image = "registry.k8s.io/pause:3.9" 由3.8修改為3.9

2.1.3 Containerd啟動(dòng)及開機(jī)自啟動(dòng)

# systemctl enable --now containerd

驗(yàn)證其版本
# containerd --version

2.2 runc準(zhǔn)備

2.2.1 libseccomp準(zhǔn)備

# wget https://github.com/opencontainers/runc/releases/download/v1.1.5/libseccomp-2.5.4.tar.gz

# tar xf libseccomp-2.5.4.tar.gz

# cd libseccomp-2.5.4/

# yum install gperf -y

# ./configure && make && make install

# find / -name "libseccomp.so"

2.2.2 runc安裝

# wget https://github.com/opencontainers/runc/releases/download/v1.1.5/runc.amd64

# chmod +x runc.amd64

查找containerd安裝時(shí)已安裝的runc所在的位置，然后替換
# which runc

替換containerd安裝已安裝的runc
# mv runc.amd64 /usr/local/sbin/runc

執(zhí)行runc命令，如果有命令幫助則為正常
# runc

如果運(yùn)行runc命令時(shí)提示：runc: error while loading shared libraries: libseccomp.so.2: cannot open shared object file: No such file or directory，則表明runc沒(méi)有找到libseccomp，需要檢查libseccomp是否安裝，本次安裝默認(rèn)就可以查詢到。

三、K8S集群部署

3.1 K8S集群軟件YUM源準(zhǔn)備

# cat > /etc/yum.repos.d/k8s.repo <<EOF
[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
EOF

3.2 K8S集群軟件安裝

3.2.1 集群軟件安裝

所有節(jié)點(diǎn)均要安裝

安裝方法-：

默認(rèn)安裝
# yum -y install kubeadm kubelet kubectl

安裝方法二：

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


安裝指定版本
# yum -y install ?kubeadm-1.27.3-0 ?kubelet-1.27.3-0 kubectl-1.27.3-0

3.2.2 配置kubelet

為了實(shí)現(xiàn)docker使用的cgroupdriver與kubelet使用的cgroup的一致性，建議修改如下文件內(nèi)容。

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


設(shè)置kubelet為開機(jī)自啟動(dòng)即可，由于沒(méi)有生成配置文件，集群初始化后自動(dòng)啟動(dòng)
# systemctl enable kubelet

3.3 K8S集群初始化

[root@master01 ~]# kubeadm init --kubernetes-version=v1.27.3 --pod-network-cidr=10.200.0.0/16 --apiserver-advertise-address=192.168.1.110 --cri-socket unix:///var/run/containerd/containerd.sock

[init] Using Kubernetes version: v1.27.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 [master01 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 192.168.10.160]
[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 [master01 localhost] and IPs [192.168.10.160 127.0.0.1 ::1]
[certs] Generating "etcd/peer" certificate and key
[certs] etcd/peer serving cert is signed for DNS names [master01 localhost] and IPs [192.168.10.160 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 20.502191 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 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 master01 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]
[bootstrap-token] Using token: hd74hg.r8l1pe4tivwyjz73
[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.1.110:6443 --token pm3ekl.y03qqkqxix111zp4 \
--discovery-token-ca-cert-hash sha256:c4aa683f5a5d7dc805e1c7966b8495485ff61cca88537f091c5bd7c996e8dbec

[root@worker01 ~]# mkdir /root/.kube

[root@worker01 ~]# cp -i /etc/kubernetes/admin.conf /root/.kube/config

3.4 工作節(jié)點(diǎn)加入集群

[root@worker01 ~]# kubeadm join 192.168.1.110:6443 --token pm3ekl.y03qqkqxix111zp4 \
> --discovery-token-ca-cert-hash sha256:c4aa683f5a5d7dc805e1c7966b8495485ff61cca88537f091c5bd7c996e8dbec --cri-socket unix:///var/run/containerd/containerd.sock

[root@worker02 ~]# kubeadm join 192.168.1.110:6443 --token pm3ekl.y03qqkqxix111zp4 \
> --discovery-token-ca-cert-hash sha256:c4aa683f5a5d7dc805e1c7966b8495485ff61cca88537f091c5bd7c996e8dbec --cri-socket unix:///var/run/containerd/containerd.sock

3.5 驗(yàn)證K8S集群節(jié)點(diǎn)是否可用

[root@master01 ~]# kubectl get nodes
NAME STATUS ROLES AGE VERSION
master01 Ready control-plane 15m v1.27.3
worker01 Ready <none> 13m v1.27.3
worker02 Ready <none> 13m v1.27.3

四、網(wǎng)絡(luò)插件calico部署

calico訪問(wèn)鏈接：https://projectcalico.docs.tigera.io/about/about-calico

# wget https://raw.githubusercontent.com/projectcalico/calico/v3.25.1/manifests/tigera-operator.yaml

# wget https://raw.githubusercontent.com/projectcalico/calico/v3.25.1/manifests/custom-resources.yaml

# vim custom-resources.yaml


# cat custom-resources.yaml


# This section includes base Calico installation configuration.
# For more information, see: https://projectcalico.docs.tigera.io/master/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.200.0.0/16 修改此行內(nèi)容為初始化時(shí)定義的pod network cidr
encapsulation: VXLANCrossSubnet
natOutgoing: Enabled
nodeSelector: all()

---

# This section configures the Calico API server.
# For more information, see: https://projectcalico.docs.tigera.io/master/reference/installation/api#operator.tigera.io/v1.APIServer
apiVersion: operator.tigera.io/v1
kind: APIServer
metadata:
name: default
spec: {}

# kubectl create -f tigera-operator.yaml

。。。。。。



# kubectl create -f custom-resources.yaml

installation.operator.tigera.io/default created
apiserver.operator.tigera.io/default created

[root@master01 ~]# kubectl get pods -n calico-system
NAME READY STATUS RESTARTS AGE

calico-kube-controllers-789dc4c76b-7gt8p? ?1/1? ? ?Running? ?0? ? ? ? ? 9m

calico-node-448bf? ? ? ? ? ? ? ? ? ? ? ? ? 1/1? ? ?Running? ?0? ? ? ? ? 9m

calico-node-4hqt7? ? ? ? ? ? ? ? ? ? ? ? ? 1/1? ? ?Running? ?0? ? ? ? ? 9m

calico-node-4j84d? ? ? ? ? ? ? ? ? ? ? ? ? 1/1? ? ?Running? ?0? ? ? ? ? 9m

calico-typha-55b5588bd6-d7xrf? ? ? ? ? ? ? 1/1? ? ?Running? ?0? ? ? ? ? 9m

calico-typha-55b5588bd6-q9jtx? ? ? ? ? ? ? 1/1? ? ?Running? ?0? ? ? ? ? 9m

csi-node-driver-6zgps? ? ? ? ? ? ? ? ? ? ? 2/2? ? ?Running? ?0? ? ? ? ? 9m

csi-node-driver-9zvhr? ? ? ? ? ? ? ? ? ? ? 2/2? ? ?Running? ?0? ? ? ? ? 9m

csi-node-driver-z2cfp? ? ? ? ? ? ? ? ? ? ? 2/2? ? ?Running? ?0? ? ? ? ? 9m

?文章來(lái)源地址http://www.zghlxwxcb.cn/news/detail-553788.html

到了這里，關(guān)于kubernetes 1.27.3 集群部署方案的文章就介紹完了。如果您還想了解更多內(nèi)容，請(qǐng)?jiān)谟疑辖撬阉鱐OY模板網(wǎng)以前的文章或繼續(xù)瀏覽下面的相關(guān)文章，希望大家以后多多支持TOY模板網(wǎng)！