国产 无码 综合区,色欲AV无码国产永久播放,无码天堂亚洲国产AV,国产日韩欧美女同一区二区

  1. Toy模板網(wǎng)首頁(yè)
  2. >Toy博客

K8s集群1.27最新版二進(jìn)制高可用部署

2年前作者：風(fēng)瀟瀟.分類(lèi)：Toy博客閱讀(29)違法舉報(bào)

這篇具有很好參考價(jià)值的文章主要介紹了K8s集群1.27最新版二進(jìn)制高可用部署。希望對(duì)大家有所幫助。如果存在錯(cuò)誤或未考慮完全的地方，請(qǐng)大家不吝賜教，您也可以點(diǎn)擊"舉報(bào)違法"按鈕提交疑問(wèn)。

K8s集群1.27最新版二進(jìn)制高可用部署

二進(jìn)制方式安裝Kubernetes高可用集群，雖然安裝過(guò)程較為復(fù)雜，但這也是每個(gè)技術(shù)人員必須要掌握的內(nèi)容。同時(shí)，在安裝過(guò)程中，也可以更加深刻地理解每個(gè)組件的工作原理。

一、系統(tǒng)環(huán)境配置

(1)主機(jī)名配置

#參考設(shè)置主機(jī)名
hostnamectl set-hostname master01
?
master01
master02
master03
node01
node02
?
#配置解析
cat >> /etc/hosts <<'EOF'
10.0.0.211  master01
10.0.0.212  master02
10.0.0.213  master03
10.0.0.214  node01
10.0.0.215  node02
EOF

(2)所有節(jié)點(diǎn)修改yum源

所有節(jié)點(diǎn)CentOS 7安裝yum源如下:
curl -o /etc/yum.repos.d/CentOS-Base.repo https://mirrors.aliyun.com/repo/Centos-7.repo
?
sed -i -e '/mirrors.cloud.aliyuncs.com/d' -e '/mirrors.aliyuncs.com/d' /etc/yum.repos.d/CentOS-Base.repo
?
curl -o /etc/yum.repos.d/docker-ce.repo https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo

(3)所有節(jié)點(diǎn)安裝常用軟件

yum -y install bind-utils expect rsync wget jq psmisc vim net-tools telnet yum-utils device-mapper-persistent-data lvm2 git ntpdate
?

?

(4)將master01節(jié)點(diǎn)配置免密碼登錄其他節(jié)點(diǎn)

cat > password_login.sh <<'EOF'
#!/bin/bash
# 創(chuàng)建密鑰對(duì)
ssh-keygen -t rsa -P "" -f /root/.ssh/id_rsa -q
?
# 聲明你服務(wù)器密碼，建議所有節(jié)點(diǎn)的密碼均一致，否則該腳本需要再次進(jìn)行優(yōu)化
export mypasswd=123.com
?
# 定義主機(jī)列表
k8s_host_list=(master01 master02 master03 node01 node02)
?
# 配置免密登錄，利用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
?
sh password_login.sh

(5)編寫(xiě)數(shù)據(jù)同步腳本

cat > /usr/local/sbin/data_rsync.sh <<'EOF'
#!/bin/bash
?
if  [ $# -ne 1 ];then
 ? echo "Usage: $0 /path/to/file(絕對(duì)路徑)"
 ? exit
fi 
?
if [ ! -e $1 ];then
 ? ?echo "[ $1 ] dir or file not find!"
 ? ?exit
fi
?
fullpath=`dirname $1`
?
basename=`basename $1`
?
cd $fullpath
?
k8s_host_list=(master01 master02 master03 node01 node02)
?
for host in ${k8s_host_list[@]};do
  tput setaf 2
 ? ?echo ===== rsyncing ${host}: $basename =====
 ?  tput setaf 7
 ?  rsync -az $basename ?`whoami`@${host}:$fullpath
 ? ?if [ $? -eq 0 ];then
 ? ? ?echo "命令執(zhí)行成功!"
 ? ?fi
done
EOF
?
chmod +x /usr/local/sbin/data_rsync.sh

二、系統(tǒng)環(huán)境優(yōu)化

基礎(chǔ)優(yōu)化

(1)所有節(jié)點(diǎn)關(guān)閉firewalld，selinux，NetworkManager

systemctl disable --now firewalld 
systemctl disable --now NetworkManager
setenforce 0
sed -i 's#SELINUX=enforcing#SELINUX=disabled#g' /etc/sysconfig/selinux
sed -i 's#SELINUX=enforcing#SELINUX=disabled#g' /etc/selinux/config

(2)所有節(jié)點(diǎn)關(guān)閉swap分區(qū)，fstab注釋swap

swapoff -a && sysctl -w vm.swappiness=0
sed -ri '/^[^#]*swap/s@^@#@' /etc/fstab
free -h

(3)所有節(jié)點(diǎn)同步時(shí)間

手動(dòng)同步時(shí)區(qū)和時(shí)間
ln -svf /usr/share/zoneinfo/Asia/Shanghai /etc/localtime
ntpdate ntp.aliyun.com
?
        - 定期任務(wù)同步("crontab -e")
*/5 * * * * /usr/sbin/ntpdate ntp.aliyun.com

(4)所有節(jié)點(diǎn)配置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

(5)所有節(jié)點(diǎn)優(yōu)化sshd服務(wù)

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選項(xiàng):
	打開(kāi)狀態(tài)下，當(dāng)客戶端試圖登錄SSH服務(wù)器時(shí)，服務(wù)器端先根據(jù)客戶端的IP地址進(jìn)行DNS PTR反向查詢(xún)出客戶端的主機(jī)名，然后根據(jù)查詢(xún)出的客戶端主機(jī)名進(jìn)行DNS正向A記錄查詢(xún)，驗(yàn)證與其原始IP地址是否一致，這是防止客戶端欺騙的一種措施，但一般我們的是動(dòng)態(tài)IP不會(huì)有PTR記錄，打開(kāi)這個(gè)選項(xiàng)不過(guò)是在白白浪費(fèi)時(shí)間而已，不如將其關(guān)閉。

		- GSSAPIAuthentication:
	當(dāng)這個(gè)參數(shù)開(kāi)啟（ GSSAPIAuthentication  yes ）的時(shí)候，通過(guò)SSH登陸服務(wù)器時(shí)候會(huì)有些會(huì)很慢！這是由于服務(wù)器端啟用了GSSAPI。登陸的時(shí)候客戶端需要對(duì)服務(wù)器端的IP地址進(jìn)行反解析，如果服務(wù)器的IP地址沒(méi)有配置PTR記錄，那么就容易在這里卡住了。

(6)Linux內(nèi)核調(diào)優(yōu)

cat > /etc/sysctl.d/k8s.conf <<'EOF'
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

升級(jí)內(nèi)核

為了集群的穩(wěn)定性和兼容性，生產(chǎn)環(huán)境的內(nèi)核最好升級(jí)到4.18版本以上

(1)下載并安裝內(nèi)核軟件包
wget http://193.49.22.109/elrepo/kernel/el7/x86_64/RPMS/kernel-ml-devel-4.19.12-1.el7.elrepo.x86_64.rpm
wget http://193.49.22.109/elrepo/kernel/el7/x86_64/RPMS/kernel-ml-4.19.12-1.el7.elrepo.x86_64.rpm
yum -y localinstall kernel-ml*

(2)更改內(nèi)核啟動(dòng)順序
grub2-set-default  0 && grub2-mkconfig -o /etc/grub2.cfg
grubby --args="user_namespace.enable=1" --update-kernel="$(grubby --default-kernel)"
grubby --default-kernel

(3)更新軟件版本，但不需要更新內(nèi)核，因?yàn)閮?nèi)核已經(jīng)更新到了指定的版本
yum -y update --exclude=kernel*

安裝ipvsadm

(1)安裝ipvsadm等相關(guān)工具
yum -y install ipvsadm ipset sysstat conntrack libseccomp 

(2)手動(dòng)加載模塊
modprobe -- ip_vs
modprobe -- ip_vs_rr
modprobe -- ip_vs_wrr
modprobe -- ip_vs_sh
modprobe -- nf_conntrack

(3)創(chuàng)建要開(kāi)機(jī)自動(dòng)加載的模塊配置文件
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)啟動(dòng)模塊，如上圖所示，這是Linux 3.10.X系列的內(nèi)核模塊，并不是我們需要的!
lsmod | grep --color=auto -e ip_vs -e nf_conntrack


溫馨提示:
	在內(nèi)核4.19+版本nf_conntrack_ipv4已經(jīng)改為nf_conntrack，4.18以下版本使用nf_conntrack_ipv4即可

重啟集群

(1)查看現(xiàn)有內(nèi)核版本
uname -r

(2)檢查默認(rèn)加載的內(nèi)核版本
grubby --default-kernel

(3)重啟所有節(jié)點(diǎn)
reboot

(4)檢查支持ipvs的內(nèi)核模塊是否加載成功，如上圖所示，支持了更多的內(nèi)核參數(shù)。
lsmod | grep --color=auto -e ip_vs -e nf_conntrack

(5)再次查看內(nèi)核版本
uname -r

升級(jí)前

K8s集群1.27最新版二進(jìn)制高可用部署

?

升級(jí)后驗(yàn)證

K8s集群1.27最新版二進(jìn)制高可用部署

?

三、基礎(chǔ)組件安裝

所有節(jié)點(diǎn)部署containerd環(huán)境

#加載 containerd模塊
cat >/etc/modules-load.d/containerd.conf<<'EOF'
overlay
br_netfilter
EOF

systemctl restart systemd-modules-load.service


cat >/etc/sysctl.d/99-kubernetes-cri.conf<<'EOF'
net.bridge.bridge-nf-call-iptables  = 1
net.ipv4.ip_forward                 = 1
net.bridge.bridge-nf-call-ip6tables = 1
EOF
 
# 加載內(nèi)核
 sysctl --system

#獲取阿里云YUM源
wget -O /etc/yum.repos.d/docker-ce.repo https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo

#查看YUM源中Containerd軟件
yum list | grep containerd
containerd.io.x86_64                        1.4.12-3.1.el7             docker-ce-stable

#下載安裝：
yum install -y containerd.io



生成containerd的配置文件

#創(chuàng)建目錄
mkdir /etc/containerd -p && containerd config default > /etc/containerd/config.toml
#生成配置文件
containerd config default > /etc/containerd/config.toml
#編輯配置文件
vim /etc/containerd/config.toml
-----
SystemdCgroup = false 改為 SystemdCgroup = true


# sandbox_image = "k8s.gcr.io/pause:3.6"
改為：
sandbox_image = "registry.aliyuncs.com/google_containers/pause:3.6"


#啟動(dòng)
systemctl enable --now  containerd

systemctl status containerd
 
#驗(yàn)證
ctr version
runc -version

部署etcd和K8S程序(所有master節(jié)點(diǎn))

(1)下載K8S，etcd的軟件包
wget https://dl.k8s.io/v1.27.1/kubernetes-server-linux-amd64.tar.gz
wget https://github.com/etcd-io/etcd/releases/download/v3.5.8/etcd-v3.5.8-linux-amd64.tar.gz


(2)解壓K8S的二進(jìn)制程序包到PATH環(huán)境變量路徑
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}


(3)解壓etcd的二進(jìn)制程序包到PATH環(huán)境變量路徑
tar -xf etcd-v3.5.8-linux-amd64.tar.gz --strip-components=1 -C /usr/local/bin etcd-v3.5.8-linux-amd64/etcd{,ctl}


(4)將組建發(fā)送到其他節(jié)點(diǎn)
MasterNodes='master02 master03'
WorkNodes='node01 node02'
for NODE in $MasterNodes; do echo $NODE; scp /usr/local/bin/kube{let,ctl,-apiserver,-controller-manager,-scheduler,-proxy} $NODE:/usr/local/bin/; scp /usr/local/bin/etcd* $NODE:/usr/local/bin/; done
for NODE in $WorkNodes; do     scp /usr/local/bin/kube{let,-proxy} $NODE:/usr/local/bin/ ; done


(5)查看kubernetes的版本
kube-apiserver --version
kube-controller-manager --version
kube-scheduler --version
etcdctl version
kubelet --version
kube-proxy --version
kubectl version


(6)所有節(jié)點(diǎn)創(chuàng)建工作目錄
mkdir -p /opt/cni/bin


(7)切換分支，版本取決于所部署的K8S版本
git clone https://gitee.com/dukuan/k8s-ha-install.git
cd k8s-ha-install/
git checkout manual-installation-v1.27.x

四、生成K8S集群證書(shū)文件

以下操作均在master01完成即可

master01下載證書(shū)管理工具

(1)master01節(jié)點(diǎn)下載證書(shū)管理工具
wget "https://pkg.cfssl.org/R1.2/cfssl_linux-amd64" -O /usr/local/bin/cfssl
wget "https://pkg.cfssl.org/R1.2/cfssljson_linux-amd64" -O /usr/local/bin/cfssljson
chmod +x /usr/local/bin/cfssl /usr/local/bin/cfssljson

(2)所有Master節(jié)點(diǎn)創(chuàng)建etcd證書(shū)目錄
mkdir /etc/etcd/ssl -p

(3)所有節(jié)點(diǎn)創(chuàng)建kubernetes相關(guān)目錄
mkdir -p /etc/kubernetes/pki

master01生成etcd證書(shū)

(1)生成etcd CA證書(shū)和CA證書(shū)的key
cd /root/k8s-ha-install/pki
cfssl gencert -initca etcd-ca-csr.json | cfssljson -bare /etc/etcd/ssl/etcd-ca


(2)頒發(fā)證書(shū)
cfssl gencert \
   -ca=/etc/etcd/ssl/etcd-ca.pem \
   -ca-key=/etc/etcd/ssl/etcd-ca-key.pem \
   -config=ca-config.json \
   -hostname=127.0.0.1,master01,master02,master03,10.0.0.211,10.0.0.212,10.0.0.213 \
   -profile=kubernetes \
   etcd-csr.json | cfssljson -bare /etc/etcd/ssl/etcd

(3)將證書(shū)復(fù)制到其他節(jié)點(diǎn)
MasterNodes='master02 master03'

for NODE in $MasterNodes; do
     ssh $NODE "mkdir -p /etc/etcd/ssl"
     for FILE in etcd-ca-key.pem  etcd-ca.pem  etcd-key.pem  etcd.pem; do
       scp /etc/etcd/ssl/${FILE} $NODE:/etc/etcd/ssl/${FILE}
     done
 done

k8s組件apiserver相關(guān)證書(shū)

(1)生成kubernetes證書(shū)
cd /root/k8s-ha-install/pki
cfssl gencert -initca ca-csr.json | cfssljson -bare /etc/kubernetes/pki/ca


(2)生成apiserver的客戶端證書(shū)
cfssl gencert   -ca=/etc/kubernetes/pki/ca.pem   -ca-key=/etc/kubernetes/pki/ca-key.pem   -config=ca-config.json   -hostname=10.96.0.1,10.0.0.101,127.0.0.1,kubernetes,kubernetes.default,kubernetes.default.svc,kubernetes.default.svc.cluster,kubernetes.default.svc.cluster.local,10.0.0.211,10.0.0.212,10.0.0.213   -profile=kubernetes   apiserver-csr.json | cfssljson -bare /etc/kubernetes/pki/apiserver

(3)生成apiserver的聚合證書(shū)
cfssl gencert   -initca front-proxy-ca-csr.json | cfssljson -bare /etc/kubernetes/pki/front-proxy-ca 
cfssl gencert   -ca=/etc/kubernetes/pki/front-proxy-ca.pem   -ca-key=/etc/kubernetes/pki/front-proxy-ca-key.pem   -config=ca-config.json   -profile=kubernetes   front-proxy-client-csr.json | cfssljson -bare /etc/kubernetes/pki/front-proxy-client


溫馨提示:
	(1)"10.96.0.0"是k8s service的網(wǎng)段，如果說(shuō)需要更改k8s service網(wǎng)段，那就需要更改"10.96.0.1";
	(2)如果不是高可用集群，10.0.0.101為Master01的IP，我這里這個(gè)是高可用的vip;

k8s組件controller manager相關(guān)證書(shū)

生成 controller-manage的證書(shū)
cfssl gencert \
   -ca=/etc/kubernetes/pki/ca.pem \
   -ca-key=/etc/kubernetes/pki/ca-key.pem \
   -config=ca-config.json \
   -profile=kubernetes \
   manager-csr.json | cfssljson -bare /etc/kubernetes/pki/controller-manager


# 注意，如果不是高可用集群，10.0.0.101:6443改為master01的地址，6443改為apiserver的端口，默認(rèn)是6443
# set-cluster：設(shè)置一個(gè)集群項(xiàng)
kubectl config set-cluster kubernetes \
     --certificate-authority=/etc/kubernetes/pki/ca.pem \
     --embed-certs=true \
     --server=https://10.0.0.101:6443 \
     --kubeconfig=/etc/kubernetes/controller-manager.kubeconfig

# set-credentials 設(shè)置一個(gè)用戶項(xiàng)
kubectl config set-credentials system:kube-controller-manager \
     --client-certificate=/etc/kubernetes/pki/controller-manager.pem \
     --client-key=/etc/kubernetes/pki/controller-manager-key.pem \
     --embed-certs=true \
     --kubeconfig=/etc/kubernetes/controller-manager.kubeconfig

# 設(shè)置一個(gè)環(huán)境項(xiàng)，一個(gè)上下文
kubectl config set-context system:kube-controller-manager@kubernetes \
    --cluster=kubernetes \
    --user=system:kube-controller-manager \
    --kubeconfig=/etc/kubernetes/controller-manager.kubeconfig

# 使用某個(gè)環(huán)境當(dāng)做默認(rèn)環(huán)境
kubectl config use-context system:kube-controller-manager@kubernetes \
     --kubeconfig=/etc/kubernetes/controller-manager.kubeconfig

k8s組件scheduler相關(guān)證書(shū)

cfssl gencert \
   -ca=/etc/kubernetes/pki/ca.pem \
   -ca-key=/etc/kubernetes/pki/ca-key.pem \
   -config=ca-config.json \
   -profile=kubernetes \
   scheduler-csr.json | cfssljson -bare /etc/kubernetes/pki/scheduler

# 注意，如果不是高可用集群，10.0.0.101:6443改為master01的地址，6443改為apiserver的端口，默認(rèn)是6443
kubectl config set-cluster kubernetes \
     --certificate-authority=/etc/kubernetes/pki/ca.pem \
     --embed-certs=true \
     --server=https://10.0.0.101:6443 \
     --kubeconfig=/etc/kubernetes/scheduler.kubeconfig

kubectl config set-credentials system:kube-scheduler \
     --client-certificate=/etc/kubernetes/pki/scheduler.pem \
     --client-key=/etc/kubernetes/pki/scheduler-key.pem \
     --embed-certs=true \
     --kubeconfig=/etc/kubernetes/scheduler.kubeconfig

kubectl config set-context system:kube-scheduler@kubernetes \
     --cluster=kubernetes \
     --user=system:kube-scheduler \
     --kubeconfig=/etc/kubernetes/scheduler.kubeconfig

kubectl config use-context system:kube-scheduler@kubernetes \
     --kubeconfig=/etc/kubernetes/scheduler.kubeconfig

生成admin的證書(shū)

cfssl gencert \
   -ca=/etc/kubernetes/pki/ca.pem \
   -ca-key=/etc/kubernetes/pki/ca-key.pem \
   -config=ca-config.json \
   -profile=kubernetes \
   admin-csr.json | cfssljson -bare /etc/kubernetes/pki/admin

# 注意，如果不是高可用集群，10.0.0.101:6443改為master01的地址，6443改為apiserver的端口，默認(rèn)是6443
kubectl config set-cluster kubernetes     --certificate-authority=/etc/kubernetes/pki/ca.pem     --embed-certs=true     --server=https://10.0.0.101:6443     --kubeconfig=/etc/kubernetes/admin.kubeconfig

kubectl config set-credentials kubernetes-admin     --client-certificate=/etc/kubernetes/pki/admin.pem     --client-key=/etc/kubernetes/pki/admin-key.pem     --embed-certs=true     --kubeconfig=/etc/kubernetes/admin.kubeconfig

kubectl config set-context kubernetes-admin@kubernetes     --cluster=kubernetes     --user=kubernetes-admin     --kubeconfig=/etc/kubernetes/admin.kubeconfig

kubectl config use-context kubernetes-admin@kubernetes     --kubeconfig=/etc/kubernetes/admin.kubeconfig



溫馨提示:
	我們用同樣的命令生成了admin.kubeconfig，scheduler.kubeconfig，controller-manager.kubeconfig，它們之間是如何區(qū)分的？
	
	我們生成的證書(shū)會(huì)定義一個(gè)用戶 admin，它是屬于 system:masters 這個(gè)組，k8s 安裝的時(shí)候會(huì)有一個(gè) clusterrole，它是一個(gè)集群角色，相當(dāng)于一個(gè)配置，它有著集群最高的管理權(quán)限，同時(shí)會(huì)創(chuàng)建一個(gè) clusterrolebinding，它會(huì)把 admin 綁到 system:masters 這個(gè)組上，然后這個(gè)組上的所有用戶都會(huì)有這個(gè)集群的權(quán)限

創(chuàng)建ServiceAccount Key

(1)ServiceAccount是k8s一種認(rèn)證方式，創(chuàng)建ServiceAccount的時(shí)候會(huì)創(chuàng)建一個(gè)與之綁定的secret，這個(gè)secret會(huì)生成一個(gè)token
openssl genrsa -out /etc/kubernetes/pki/sa.key 2048
openssl rsa -in /etc/kubernetes/pki/sa.key -pubout -out /etc/kubernetes/pki/sa.pub


(2)發(fā)送證書(shū)至其他節(jié)點(diǎn)
for NODE in master02 master03; 
  do 
	 for FILE in $(ls /etc/kubernetes/pki | grep -v etcd); 
	 do 
		scp /etc/kubernetes/pki/${FILE} $NODE:/etc/kubernetes/pki/${FILE};
	 done; 
	 for FILE in admin.kubeconfig controller-manager.kubeconfig scheduler.kubeconfig; 
	 do 
		scp /etc/kubernetes/${FILE} $NODE:/etc/kubernetes/${FILE};
	 done;
done

五、etcd配置

1.master節(jié)點(diǎn)分別創(chuàng)建配置文件

master01節(jié)點(diǎn)的配置文件

cat > /etc/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.0.211:2380'
listen-client-urls: 'https://10.0.0.211:2379,http://127.0.0.1:2379'
max-snapshots: 3
max-wals: 5
cors:
initial-advertise-peer-urls: 'https://10.0.0.211:2380'
advertise-client-urls: 'https://10.0.0.211:2379'
discovery:
discovery-fallback: 'proxy'
discovery-proxy:
discovery-srv:
initial-cluster: 'master01=https://10.0.0.211:2380,master02=https://10.0.0.212:2380,master03=https://10.0.0.213: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: '/etc/kubernetes/pki/etcd/etcd.pem'
  key-file: '/etc/kubernetes/pki/etcd/etcd-key.pem'
  client-cert-auth: true
  trusted-ca-file: '/etc/kubernetes/pki/etcd/etcd-ca.pem'
  auto-tls: true
peer-transport-security:
  cert-file: '/etc/kubernetes/pki/etcd/etcd.pem'
  key-file: '/etc/kubernetes/pki/etcd/etcd-key.pem'
  peer-client-cert-auth: true
  trusted-ca-file: '/etc/kubernetes/pki/etcd/etcd-ca.pem'
  auto-tls: true
debug: false
log-package-levels:
log-outputs: [default]
force-new-cluster: false
EOF

master02節(jié)點(diǎn)的配置文件

cat > /etc/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.0.212:2380'
listen-client-urls: 'https://10.0.0.212:2379,http://127.0.0.1:2379'
max-snapshots: 3
max-wals: 5
cors:
initial-advertise-peer-urls: 'https://10.0.0.212:2380'
advertise-client-urls: 'https://10.0.0.212:2379'
discovery:
discovery-fallback: 'proxy'
discovery-proxy:
discovery-srv:
initial-cluster: 'master01=https://10.0.0.211:2380,master02=https://10.0.0.212:2380,master03=https://10.0.0.213: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: '/etc/kubernetes/pki/etcd/etcd.pem'
  key-file: '/etc/kubernetes/pki/etcd/etcd-key.pem'
  client-cert-auth: true
  trusted-ca-file: '/etc/kubernetes/pki/etcd/etcd-ca.pem'
  auto-tls: true
peer-transport-security:
  cert-file: '/etc/kubernetes/pki/etcd/etcd.pem'
  key-file: '/etc/kubernetes/pki/etcd/etcd-key.pem'
  peer-client-cert-auth: true
  trusted-ca-file: '/etc/kubernetes/pki/etcd/etcd-ca.pem'
  auto-tls: true
debug: false
log-package-levels:
log-outputs: [default]
force-new-cluster: false
EOF

master03節(jié)點(diǎn)的配置文件

cat > /etc/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.0.213:2380'
listen-client-urls: 'https://10.0.0.213:2379,http://127.0.0.1:2379'
max-snapshots: 3
max-wals: 5
cors:
initial-advertise-peer-urls: 'https://10.0.0.213:2380'
advertise-client-urls: 'https://10.0.0.213:2379'
discovery:
discovery-fallback: 'proxy'
discovery-proxy:
discovery-srv:
initial-cluster: 'master01=https://10.0.0.211:2380,master02=https://10.0.0.212:2380,master03=https://10.0.0.213: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: '/etc/kubernetes/pki/etcd/etcd.pem'
  key-file: '/etc/kubernetes/pki/etcd/etcd-key.pem'
  client-cert-auth: true
  trusted-ca-file: '/etc/kubernetes/pki/etcd/etcd-ca.pem'
  auto-tls: true
peer-transport-security:
  cert-file: '/etc/kubernetes/pki/etcd/etcd.pem'
  key-file: '/etc/kubernetes/pki/etcd/etcd-key.pem'
  peer-client-cert-auth: true
  trusted-ca-file: '/etc/kubernetes/pki/etcd/etcd-ca.pem'
  auto-tls: true
debug: false
log-package-levels:
log-outputs: [default]
force-new-cluster: false
EOF

2.所有master節(jié)點(diǎn)啟動(dòng)etcd服務(wù)

(1)創(chuàng)建啟動(dòng)腳本
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=/etc/etcd/etcd.config.yml
Restart=on-failure
RestartSec=10
LimitNOFILE=65536

[Install]
WantedBy=multi-user.target
Alias=etcd3.service
EOF


(2)啟動(dòng)服務(wù)
mkdir /etc/kubernetes/pki/etcd
ln -s /etc/etcd/ssl/* /etc/kubernetes/pki/etcd/
systemctl daemon-reload
systemctl enable --now etcd
systemctl status etcd

(3)查看etcd狀態(tài)
etcdctl --endpoints="10.0.0.211:2379,10.0.0.212:2379,10.0.0.213:2379" --cacert=/etc/kubernetes/pki/etcd/etcd-ca.pem --cert=/etc/kubernetes/pki/etcd/etcd.pem --key=/etc/kubernetes/pki/etcd/etcd-key.pem  endpoint status --write-out=table


溫馨提示:
	etcd集群?jiǎn)?dòng)成功如圖所示。

K8s集群1.27最新版二進(jìn)制高可用部署

?

六、高可用配置

（haproxy+keepalived）

1.所有master節(jié)點(diǎn)安裝keepalived和haproxy

yum -y install keepalived haproxy

2.所有master節(jié)點(diǎn)配置haproxy，配置文件各個(gè)節(jié)點(diǎn)相同

(1)備份配置文件
cp /etc/haproxy/haproxy.cfg{,`date +%F`}


(2)所有節(jié)點(diǎn)的配置文件內(nèi)容相同
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 master01   10.0.0.211:6443  check
  server master02   10.0.0.212:6443  check
  server master03   10.0.0.213:6443  check
EOF

3.所有master節(jié)點(diǎn)配置keepalived，配置文件各節(jié)點(diǎn)不同

備份配置文件

cp /etc/keepalived/keepalived.conf{,`date +%F`}

"master01"節(jié)點(diǎn)創(chuàng)建配置文件

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 10.0.0.211
    virtual_router_id 51
    priority 101
    advert_int 2
    authentication {
        auth_type PASS
        auth_pass K8SHA_KA_AUTH
    }
    virtual_ipaddress {
        10.0.0.101
    }
    track_script {
       chk_apiserver
    }
}
EOF

"master02"節(jié)點(diǎn)創(chuàng)建配置文件

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 10.0.0.212
    virtual_router_id 51
    priority 101
    advert_int 2
    authentication {
        auth_type PASS
        auth_pass K8SHA_KA_AUTH
    }
    virtual_ipaddress {
        10.0.0.101
    }
    track_script {
       chk_apiserver
    }
}
EOF

"master03"節(jié)點(diǎn)創(chuàng)建配置文件

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 10.0.0.213
    virtual_router_id 51
    priority 101
    advert_int 2
    authentication {
        auth_type PASS
        auth_pass K8SHA_KA_AUTH
    }
    virtual_ipaddress {
        10.0.0.101
    }
    track_script {
       chk_apiserver
    }
}
EOF

溫馨提示： 上述keepalived配置文件中的網(wǎng)卡名稱(chēng)是ens33，如果你的網(wǎng)卡名稱(chēng)是eth0，需要修改配置文件，否則keepalived啟動(dòng)后會(huì)自動(dòng)退出或沒(méi)有VIP

4.所有master節(jié)點(diǎn)配置KeepAlived健康檢查文件

(1)創(chuàng)建檢查腳本
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


(2)添加執(zhí)行權(quán)限
chmod +x /etc/keepalived/check_apiserver.sh

溫馨提示:
	(1)我們通過(guò)KeepAlived虛擬出來(lái)一個(gè)VIP，VIP會(huì)配置到一個(gè)master節(jié)點(diǎn)上面，它會(huì)通過(guò)haproxy暴露的16443的端口反向代理到我們的三個(gè)master節(jié)點(diǎn)上面，所以我們可以通過(guò)VIP的地址加上16443訪問(wèn)到我們的API server;
	(2)健康檢查會(huì)檢查haproxy的狀態(tài)，三次失敗就會(huì)將KeepAlived停掉，停掉之后KeepAlived會(huì)跳到其他的節(jié)點(diǎn);

5.啟動(dòng)服務(wù)

(1)啟動(dòng)harproxy
systemctl daemon-reload
systemctl enable --now haproxy

(2)啟動(dòng)keepalived
systemctl enable --now keepalived
systemctl status keepalived

(3)查看VIP，如圖所示
ip a


(4) 修改過(guò)網(wǎng)卡名執(zhí)行此操作
sed -i  's#ens33#eth0#g' /etc/keepalived/keepalived.conf
systemctl restart keepalived.service

K8s集群1.27最新版二進(jìn)制高可用部署

?

七、二進(jìn)制K8smaster組件配置

所有master節(jié)點(diǎn)啟動(dòng)Apiserver服務(wù)

#所有節(jié)點(diǎn)執(zhí)行
(1)所有節(jié)點(diǎn)(k8s-master0[1-3])創(chuàng)建工作目錄
mkdir -p /etc/kubernetes/manifests/ /etc/systemd/system/kubelet.service.d /var/lib/kubelet /var/log/kubernetes

#master01執(zhí)行
(2)master01節(jié)點(diǎn)創(chuàng)建配置文件
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  \
      --allow-privileged=true  \
      --bind-address=0.0.0.0  \
      --secure-port=6443  \
      --advertise-address=10.0.0.211 \
      --service-cluster-ip-range=10.96.0.0/12  \
      --service-node-port-range=30000-32767  \
      --etcd-servers=https://10.0.0.211:2379,https://10.0.0.212:2379,https://10.0.0.213:2379 \
      --etcd-cafile=/etc/etcd/ssl/etcd-ca.pem  \
      --etcd-certfile=/etc/etcd/ssl/etcd.pem  \
      --etcd-keyfile=/etc/etcd/ssl/etcd-key.pem  \
      --client-ca-file=/etc/kubernetes/pki/ca.pem  \
      --tls-cert-file=/etc/kubernetes/pki/apiserver.pem  \
      --tls-private-key-file=/etc/kubernetes/pki/apiserver-key.pem  \
      --kubelet-client-certificate=/etc/kubernetes/pki/apiserver.pem  \
      --kubelet-client-key=/etc/kubernetes/pki/apiserver-key.pem  \
      --service-account-key-file=/etc/kubernetes/pki/sa.pub  \
      --service-account-signing-key-file=/etc/kubernetes/pki/sa.key  \
      --service-account-issuer=https://kubernetes.default.svc.cluster.local \
      --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=/etc/kubernetes/pki/front-proxy-ca.pem  \
      --proxy-client-cert-file=/etc/kubernetes/pki/front-proxy-client.pem  \
      --proxy-client-key-file=/etc/kubernetes/pki/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 
      # --token-auth-file=/etc/kubernetes/token.csv  

Restart=on-failure
RestartSec=10s
LimitNOFILE=65535

[Install]
WantedBy=multi-user.target
EOF


#master02執(zhí)行
(3)master02節(jié)點(diǎn)創(chuàng)建配置文件
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  \
      --allow-privileged=true  \
      --bind-address=0.0.0.0  \
      --secure-port=6443  \
      --advertise-address=10.0.0.212 \
      --service-cluster-ip-range=10.96.0.0/12  \
      --service-node-port-range=30000-32767  \
      --etcd-servers=https://10.0.0.211:2379,https://10.0.0.212:2379,https://10.0.0.213:2379 \
      --etcd-cafile=/etc/etcd/ssl/etcd-ca.pem  \
      --etcd-certfile=/etc/etcd/ssl/etcd.pem  \
      --etcd-keyfile=/etc/etcd/ssl/etcd-key.pem  \
      --client-ca-file=/etc/kubernetes/pki/ca.pem  \
      --tls-cert-file=/etc/kubernetes/pki/apiserver.pem  \
      --tls-private-key-file=/etc/kubernetes/pki/apiserver-key.pem  \
      --kubelet-client-certificate=/etc/kubernetes/pki/apiserver.pem  \
      --kubelet-client-key=/etc/kubernetes/pki/apiserver-key.pem  \
      --service-account-key-file=/etc/kubernetes/pki/sa.pub  \
      --service-account-signing-key-file=/etc/kubernetes/pki/sa.key  \
      --service-account-issuer=https://kubernetes.default.svc.cluster.local \
      --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=/etc/kubernetes/pki/front-proxy-ca.pem  \
      --proxy-client-cert-file=/etc/kubernetes/pki/front-proxy-client.pem  \
      --proxy-client-key-file=/etc/kubernetes/pki/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 
      # --token-auth-file=/etc/kubernetes/token.csv  

Restart=on-failure
RestartSec=10s
LimitNOFILE=65535

[Install]
WantedBy=multi-user.target
EOF


#master03執(zhí)行
(4)master03節(jié)點(diǎn)創(chuàng)建配置文件
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  \
      --allow-privileged=true  \
      --bind-address=0.0.0.0  \
      --secure-port=6443  \
      --advertise-address=10.0.0.213 \
      --service-cluster-ip-range=10.96.0.0/12  \
      --service-node-port-range=30000-32767  \
      --etcd-servers=https://10.0.0.211:2379,https://10.0.0.212:2379,https://10.0.0.213:2379 \
      --etcd-cafile=/etc/etcd/ssl/etcd-ca.pem  \
      --etcd-certfile=/etc/etcd/ssl/etcd.pem  \
      --etcd-keyfile=/etc/etcd/ssl/etcd-key.pem  \
      --client-ca-file=/etc/kubernetes/pki/ca.pem  \
      --tls-cert-file=/etc/kubernetes/pki/apiserver.pem  \
      --tls-private-key-file=/etc/kubernetes/pki/apiserver-key.pem  \
      --kubelet-client-certificate=/etc/kubernetes/pki/apiserver.pem  \
      --kubelet-client-key=/etc/kubernetes/pki/apiserver-key.pem  \
      --service-account-key-file=/etc/kubernetes/pki/sa.pub  \
      --service-account-signing-key-file=/etc/kubernetes/pki/sa.key  \
      --service-account-issuer=https://kubernetes.default.svc.cluster.local \
      --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=/etc/kubernetes/pki/front-proxy-ca.pem  \
      --proxy-client-cert-file=/etc/kubernetes/pki/front-proxy-client.pem  \
      --proxy-client-key-file=/etc/kubernetes/pki/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 
      # --token-auth-file=/etc/kubernetes/token.csv  

Restart=on-failure
RestartSec=10s
LimitNOFILE=65535

[Install]
WantedBy=multi-user.target
EOF


#所有master節(jié)點(diǎn)執(zhí)行
(5)啟動(dòng)服務(wù)
systemctl daemon-reload && systemctl enable --now kube-apiserver && systemctl status kube-apiserver

所有master節(jié)點(diǎn)啟動(dòng)ControllerManager服務(wù)

(1)所有節(jié)點(diǎn)創(chuàng)建配置文件
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 \
      --bind-address=127.0.0.1 \
      --root-ca-file=/etc/kubernetes/pki/ca.pem \
      --cluster-signing-cert-file=/etc/kubernetes/pki/ca.pem \
      --cluster-signing-key-file=/etc/kubernetes/pki/ca-key.pem \
      --service-account-private-key-file=/etc/kubernetes/pki/sa.key \
      --kubeconfig=/etc/kubernetes/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=172.16.0.0/12 \
      --requestheader-client-ca-file=/etc/kubernetes/pki/front-proxy-ca.pem \
      --node-cidr-mask-size=24
      
Restart=always
RestartSec=10s

[Install]
WantedBy=multi-user.target
EOF

(2)啟動(dòng)服務(wù)，查看狀態(tài)
systemctl daemon-reload
systemctl enable --now kube-controller-manager
systemctl  status kube-controller-manager

所有master節(jié)點(diǎn)啟動(dòng)Scheduler服務(wù)

(1)所有節(jié)點(diǎn)創(chuàng)建配置文件
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 \
     --bind-address=127.0.0.1 \
     --leader-elect=true \
     --kubeconfig=/etc/kubernetes/scheduler.kubeconfig

Restart=always
RestartSec=10s

[Install]
WantedBy=multi-user.target
EOF


(2)啟動(dòng)服務(wù)并查看狀態(tài)，如上圖所示
systemctl daemon-reload
systemctl enable --now kube-scheduler
systemctl  status kube-scheduler

八、創(chuàng)建Bootstrapping自動(dòng)頒發(fā)證書(shū)

1.master01節(jié)點(diǎn)創(chuàng)建bootstrap-kubelet.kubeconfig文件

cd /root/k8s-ha-install/bootstrap
kubectl config set-cluster kubernetes     --certificate-authority=/etc/kubernetes/pki/ca.pem     --embed-certs=true     --server=https://10.0.0.101:6443     --kubeconfig=/etc/kubernetes/bootstrap-kubelet.kubeconfig
kubectl config set-credentials tls-bootstrap-token-user     --token=c8ad9c.2e4d610cf3e7426e --kubeconfig=/etc/kubernetes/bootstrap-kubelet.kubeconfig
kubectl config set-context tls-bootstrap-token-user@kubernetes     --cluster=kubernetes     --user=tls-bootstrap-token-user     --kubeconfig=/etc/kubernetes/bootstrap-kubelet.kubeconfig
kubectl config use-context tls-bootstrap-token-user@kubernetes     --kubeconfig=/etc/kubernetes/bootstrap-kubelet.kubeconfig


溫馨提示:
	"bootstrap-kubelet.kubeconfig"是一個(gè)keepalived用來(lái)向apiserver申請(qǐng)證書(shū)的文件，如果要修改bootstrap.secret.yaml的token-id和token-secret，需要保證c8ad9c字符串一致的，并且位數(shù)是一樣的。還要保證上個(gè)命令的黃色字體：c8ad9c.2e4d610cf3e7426e與你修改的字符串要一致

2.所有master節(jié)點(diǎn)拷貝管理證書(shū)

所有master節(jié)點(diǎn)執(zhí)行此操作

mkdir -p /root/.kube ; cp /etc/kubernetes/admin.kubeconfig /root/.kube/config

3.創(chuàng)建bootstrap

kubectl create -f bootstrap.secret.yaml

九、部署Node節(jié)點(diǎn)

分發(fā)證書(shū)

cd /etc/kubernetes/
for NODE in master02 master03 node01 node02; do
     ssh $NODE mkdir -p /etc/kubernetes/pki /etc/etcd/ssl /etc/etcd/ssl
     for FILE in etcd-ca.pem etcd.pem etcd-key.pem; do
       scp /etc/etcd/ssl/$FILE $NODE:/etc/etcd/ssl/
     done
     for FILE in pki/ca.pem pki/ca-key.pem pki/front-proxy-ca.pem bootstrap-kubelet.kubeconfig; do
       scp /etc/kubernetes/$FILE $NODE:/etc/kubernetes/${FILE}
done
done


溫馨提示:
	node節(jié)點(diǎn)使用自動(dòng)頒發(fā)證書(shū)的形式配置

Kubelet配置

集群所有節(jié)點(diǎn)操作

(1)所有節(jié)點(diǎn)創(chuàng)建工作目錄
mkdir -p /var/lib/kubelet /var/log/kubernetes /etc/systemd/system/kubelet.service.d /etc/kubernetes/manifests/


(2)所有節(jié)點(diǎn)配置kubelet service
cat >  /usr/lib/systemd/system/kubelet.service <<'EOF'
[Unit]
Description=Kubernetes Kubelet
Documentation=https://github.com/kubernetes/kubernetes
After=docker.service

[Service]
ExecStart=/usr/local/bin/kubelet
Restart=always
StartLimitInterval=0
RestartSec=10

[Install]
WantedBy=multi-user.target
EOF


(3)所有節(jié)點(diǎn)配置kubelet service的配置文件
cat > /etc/systemd/system/kubelet.service.d/kubelet.conf <<'EOF'
[Service]
Environment="KUBELET_KUBECONFIG_ARGS=--bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.kubeconfig --kubeconfig=/etc/kubernetes/kubelet.kubeconfig"
Environment="KUBELET_SYSTEM_ARGS=--runtime-request-timeout=15m  --container-runtime-endpoint=unix:///run/containerd/containerd.sock"
Environment="KUBELET_CONFIG_ARGS=--config=/etc/kubernetes/kubelet-conf.yml --pod-infra-container-image=registry.aliyuncs.com/google_containers/pause-amd64:3.2"
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



(4)所有節(jié)點(diǎn)創(chuàng)建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: /etc/kubernetes/pki/ca.pem
authorization:
  mode: Webhook
  webhook:
    cacheAuthorizedTTL: 5m0s
    cacheUnauthorizedTTL: 30s
cgroupDriver: systemd
cgroupsPerQOS: true
clusterDNS:
- 10.96.0.10
clusterDomain: cluster.local
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
EOF

(5)啟動(dòng)所有節(jié)點(diǎn)kubelet
systemctl daemon-reload
systemctl enable --now kubelet
systemctl status kubelet


(6)在master101節(jié)點(diǎn)上查看node信息，如上圖所示。
kubectl get nodes

K8s集群1.27最新版二進(jìn)制高可用部署

?

kube-proxy配置

(1)在“master01”節(jié)點(diǎn)生成"/etc/kubernetes/kube-proxy.kubeconfig"配置文件
cd /root/k8s-ha-install
kubectl -n kube-system create serviceaccount kube-proxy
kubectl create clusterrolebinding system:kube-proxy         --clusterrole system:node-proxier         --serviceaccount kube-system:kube-proxy
SECRET=$(kubectl -n kube-system get sa/kube-proxy \
    --output=jsonpath='{.secrets[0].name}')
JWT_TOKEN=$(kubectl -n kube-system get secret/$SECRET \
--output=jsonpath='{.data.token}' | base64 -d)
PKI_DIR=/etc/kubernetes/pki
K8S_DIR=/etc/kubernetes
kubectl config set-cluster kubernetes     --certificate-authority=/etc/kubernetes/pki/ca.pem     --embed-certs=true     --server=https://10.0.0.101:6443     --kubeconfig=${K8S_DIR}/kube-proxy.kubeconfig
kubectl config set-credentials kubernetes     --token=${JWT_TOKEN}     --kubeconfig=/etc/kubernetes/kube-proxy.kubeconfig
kubectl config set-context kubernetes     --cluster=kubernetes     --user=kubernetes     --kubeconfig=/etc/kubernetes/kube-proxy.kubeconfig
kubectl config use-context kubernetes     --kubeconfig=/etc/kubernetes/kube-proxy.kubeconfig



(2)在“master01”將kube-proxy的systemd Service文件發(fā)送到其他節(jié)點(diǎn)
for NODE in master01 master02 master03 node01 node02; do
     scp /etc/kubernetes/kube-proxy.kubeconfig $NODE:/etc/kubernetes/kube-proxy.kubeconfig
done



(3)集群所有節(jié)點(diǎn)創(chuàng)建kube-proxy.conf配置文件
cat > /etc/kubernetes/kube-proxy.conf << EOF
KUBE_PROXY_OPTS="--v=2 \
	--config=/etc/kubernetes/kube-proxy-config.yml"
EOF
 
# 注意修改各個(gè)節(jié)點(diǎn)的"hostnameOverride"的值
cat > /etc/kubernetes/kube-proxy-config.yml << EOF
kind: KubeProxyConfiguration
apiVersion: kubeproxy.config.k8s.io/v1alpha1
bindAddress: 0.0.0.0
metricsBindAddress: 0.0.0.0:10249
clientConnection:
 kubeconfig: /etc/kubernetes/kube-proxy.kubeconfig
hostnameOverride: node02   #每個(gè)節(jié)點(diǎn)的名稱(chēng)都是不同的，注意修改
clusterCIDR: 172.30.0.0/16
EOF

 
(4)所有節(jié)點(diǎn)使用systemd管理kube-proxy
cat > /usr/lib/systemd/system/kube-proxy.service << EOF
[Unit]
Description=Kubernetes Proxy
After=network.target

[Service]
EnvironmentFile=/etc/kubernetes/kube-proxy.conf
ExecStart=/usr/local/bin/kube-proxy \$KUBE_PROXY_OPTS
Restart=on-failure
LimitNOFILE=65536

[Install]
WantedBy=multi-user.target
EOF
 
 
(5)所有節(jié)點(diǎn)啟動(dòng)kube-proxy
systemctl daemon-reload
systemctl enable --now kube-proxy
systemctl status kube-proxy



溫馨提示:
	如果更改了集群Pod的網(wǎng)段，需要更改kube-proxy.conf的clusterCIDR參數(shù)，比如我上面的案例自定義的網(wǎng)段為"172.30.0.0/16"。

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

1.部署calico網(wǎng)絡(luò)插件

cd /root/k8s-ha-install/calico/

# 更改此處為自己的pod網(wǎng)段
POD_SUBNET="172.30.0.0/16"
sed -i 's@# - name: CALICO_IPV4POOL_CIDR@- name: CALICO_IPV4POOL_CIDR@g; s@#   value: "192.168.0.0/16"@  value: '"${POD_SUBNET}"'@g' calico.yaml

kubectl apply -f calico.yaml

2.觀察各節(jié)點(diǎn)是否部署成功

kubectl get pods -A

K8s集群1.27最新版二進(jìn)制高可用部署

?

十一、附加組件部署

1.部署CoreDNS

(1)部署coreDNS
cd /root/k8s-ha-install/
修改"clusterIP"的值，如下圖：

kubectl create -f CoreDNS/coredns.yaml

(2)查看狀態(tài)
kubectl get po -n kube-system -l k8s-app=kube-dns


(3)驗(yàn)證DNS組件
dig @10.96.0.10 metrics-server.kube-system.svc.cluster.local +short

K8s集群1.27最新版二進(jìn)制高可用部署

K8s集群1.27最新版二進(jìn)制高可用部署?

?

2.部署Metrics Server

(1)部署Metrics Server
cd /root/k8s-ha-install/metrics-server
kubectl  create -f . 

(2)查看node和pod的監(jiān)控狀態(tài)
kubectl top no
kubectl top po -A

K8s集群1.27最新版二進(jìn)制高可用部署

?

3.安裝dashboard

(1)安裝dashboard服務(wù)
cd /root/k8s-ha-install/dashboard/
kubectl  create -f .


(2)查看token并訪問(wèn)dashboard，如下圖所示
kubectl get svc kubernetes-dashboard -n kubernetes-dashboard
kubectl get pod -A -o wide | grep dashboard
kubectl -n kube-system describe secret $(kubectl -n kube-system get secret | grep admin-user | awk '{print $1}')

#瀏覽器訪問(wèn)https://10.0.0.101:30069
#如果訪問(wèn)頁(yè)面出現(xiàn)不安全，鼠標(biāo)點(diǎn)擊空白處，輸入thisisunsafe即可

K8s集群1.27最新版二進(jìn)制高可用部署

K8s集群1.27最新版二進(jìn)制高可用部署?

?

十二、優(yōu)化

1.自動(dòng)補(bǔ)全功能

- docker自動(dòng)補(bǔ)全功能
yum -y install bash-completion
source /usr/share/bash-completion/bash_completion


- kubectl 自動(dòng)補(bǔ)全功能
echo "source <(kubectl completion bash)" >> ~/.bashrc && source ~/.bashrc

2.多master管理K8S集群驗(yàn)證

如果有任意一個(gè)master節(jié)點(diǎn)有問(wèn)題，請(qǐng)驗(yàn)證kubeconfig文件是否有配置。


參考指令:
	mkdir -p /root/.kube ; cp /etc/kubernetes/admin.kubeconfig /root/.kube/config

3.驗(yàn)證集群高可用

K8s集群1.27最新版二進(jìn)制高可用部署

?

如上圖所示，K8S集群的VIP最開(kāi)始在"master03"節(jié)點(diǎn)。


接下來(lái)，我們將該節(jié)點(diǎn)停機(jī)后，并不會(huì)影響K8S集群正常使用

K8s集群1.27最新版二進(jìn)制高可用部署

?

4.測(cè)試集群是否正常

創(chuàng)建一個(gè)nginx的pod資源

cat >nginx.yaml<<'EOF'
apiVersion: v1
kind: Pod
metadata:
  name: web
spec:
  containers:
  - name: nginx
    image: nginx:1.21
EOF

kubectl apply -f nginx.yaml

K8s集群1.27最新版二進(jìn)制高可用部署

?

至此，二進(jìn)制部署kubernetes高可用集群，部署完成。文章來(lái)源地址http://www.zghlxwxcb.cn/news/detail-468860.html

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

本文來(lái)自互聯(lián)網(wǎng)用戶投稿，該文觀點(diǎn)僅代表作者本人，不代表本站立場(chǎng)。本站僅提供信息存儲(chǔ)空間服務(wù)，不擁有所有權(quán)，不承擔(dān)相關(guān)法律責(zé)任。如若轉(zhuǎn)載，請(qǐng)注明出處： 如若內(nèi)容造成侵權(quán)/違法違規(guī)/事實(shí)不符，請(qǐng)點(diǎn)擊違法舉報(bào)進(jìn)行投訴反饋，一經(jīng)查實(shí)，立即刪除！

領(lǐng)支付寶紅包贊助服務(wù)器費(fèi)用

相關(guān)文章

  • 通過(guò)kubeadm部署k8s 1.27高可有集群

    通過(guò)kubeadm部署k8s 1.27高可有集群

    本次部署使用外部etcd集群+LB+K8S集群方案。如下圖： 軟件列表及軟件版本：CentOS7U9, Linux kernel 5.4,docker-ce 23.0.6,cri-dockerd v0.3.1,k8s集群為1.27.1 所有主機(jī)均需要操作。 所有主機(jī)均需要操作。 所有主機(jī)均需要操作。 修改完成后需要重啟操作系統(tǒng)，如不重啟，可臨時(shí)關(guān)閉，命令為s

    2024年02月13日
    瀏覽(28)
  • 【云原生】k8s組件&架構(gòu)介紹與K8s最新版部署

    【云原生】k8s組件&架構(gòu)介紹與K8s最新版部署

    ? ? ? 個(gè)人主頁(yè)： 征服bug-CSDN博客 kubernetes專(zhuān)欄： kubernetes_征服bug的博客-CSDN博客? 目錄 1 集群組件 1.1 控制平面組件（Control Plane Components） 1.2 Node 組件 1.3 插件 (Addons) 2 集群架構(gòu)詳細(xì) 3 集群搭建[重點(diǎn)] 3.1 minikube 3.2 裸機(jī)安裝 集群組件 核心概念 集群安裝 集群 cluster : 將同一個(gè)

    2024年02月14日
    瀏覽(90)
  • k8s1.27.2版本二進(jìn)制高可用集群部署

    k8s1.27.2版本二進(jìn)制高可用集群部署

    說(shuō)明：本次實(shí)驗(yàn)共有5臺(tái)主機(jī)，3臺(tái)master節(jié)點(diǎn)同時(shí)又是worker，os128、os129、os130 節(jié)點(diǎn)主機(jī)容器運(yùn)行時(shí)用的containerd，worker131、worker132主機(jī)的用的docker 主機(jī)名 IP 組件 系統(tǒng) os128 192.168.177.128 etcd、kube-apiserver、kube-controller-manager、kube-scheduler、kubelet、kube-proxy、containerd CentOS7.9 os129 192.16

    2024年01月22日
    瀏覽(72)

  • K8S認(rèn)證工程師(CKA)考試（最新版，實(shí)測(cè)可靠）

    k8s的全部考試答案，親測(cè)可靠，博主CKA,CKS已過(guò)，歡迎交流。（求個(gè)關(guān)注吧） 1、權(quán)限控制 RBAC 設(shè)置配置環(huán)境： [candidate@node-1] $ kubectl config use-context k8s Context 為部署流水線創(chuàng)建一個(gè)新的 ClusterRole 并將其綁定到范圍為特定的 namespace 的特定 ServiceAccount 。 Task 創(chuàng)建一個(gè)名為 deploy

    2024年04月25日
    瀏覽(27)

  • K8S認(rèn)證安全工程師(CKS)考試（最新版，實(shí)測(cè)可靠）

    k8s的全部考試答案，親測(cè)可靠，博主CKA,CKS已過(guò)，歡迎交流。（求個(gè)關(guān)注吧） 1、kube-bench 修復(fù)不安全項(xiàng) Context 針對(duì) kubeadm 創(chuàng)建的 cluster 運(yùn)行 CIS 基準(zhǔn)測(cè)試工具時(shí)，發(fā)現(xiàn)了多個(gè)必須立即解決的問(wèn)題。 Task 通過(guò)配置修復(fù)所有問(wèn)題并重新啟動(dòng)受影響的組件以確保新的設(shè)置生效。 修復(fù)

    2024年04月13日
    瀏覽(21)
  • Centos7系統(tǒng)環(huán)境下Kubernetes(K8s)默認(rèn)最新版安裝

    Centos7系統(tǒng)環(huán)境下Kubernetes(K8s)默認(rèn)最新版安裝

    說(shuō)明： 1.利用Kubeadm的方式安裝K8s 2.除關(guān)閉防護(hù)墻外，其它均可以用于生產(chǎn)環(huán)境 3.安裝最新K8s版本，如果有更新的版本，就會(huì)默認(rèn)安裝最新的版本，截止到目前最新版本是1.30 4.cri-dockerd和runc截止到目前是最新的，如果有最新版本的，根據(jù)提供的鏈接順藤摸瓜去Github上下載。 注

    2024年04月29日
    瀏覽(40)
  • 基于centos7的k8s最新版v1.29.2安裝教程

    基于centos7的k8s最新版v1.29.2安裝教程

    Kubernetes 是一個(gè)可移植、可擴(kuò)展的開(kāi)源平臺(tái)，用于管理容器化的工作負(fù)載和服務(wù)，可促進(jìn)聲明式配置和自動(dòng)化。 Kubernetes 擁有一個(gè)龐大且快速增長(zhǎng)的生態(tài)，其服務(wù)、支持和工具的使用范圍相當(dāng)廣泛。 Kubernetes ?這個(gè)名字源于希臘語(yǔ)，意為“舵手”或“飛行員”。k8s 這個(gè)縮寫(xiě)是

    2024年03月18日
    瀏覽(29)

  • K8S 1.27 新特性 Pod 無(wú)需重啟調(diào)整CPU內(nèi)存資源

    如果您已經(jīng)部署了指定 CPU 或 Memory 資源的 Kubernetes pod，可能已經(jīng)注意到更改資源值涉及重新啟動(dòng) pod。直到現(xiàn)在，這一直是運(yùn)行工作負(fù)載的破壞性操作。 在 Kubernetes v1.27 中，添加了一個(gè)新的 alpha 功能，允許用戶在不重啟容器的情況下調(diào)整分配給 Pod 的 CPU 或 memory 資源的大小。

    2024年02月11日
    瀏覽(27)

  • RockyLinux9.2安裝k8s 1.27+calico+BGP+OpenELB

    本文在rockylinux 9.2 中使用kubeadm部署 Kubernetes 1.27 、 containerd 、 calico 、 BGP 等; 使用 OpenELB 作為 LoadBalancer ; 使用 BIRD 模擬物理路由器; 使用 kube-vip 實(shí)現(xiàn) control-plane 高可用; 本文所有k8s相關(guān)組件都固定版本安裝，避免因版本更新導(dǎo)致各種問(wèn)題；如 kubelet-1.27.2 、 kubeadm-1.27.2 、 kub

    2024年02月15日
    瀏覽(24)

  • K8S 1.27 動(dòng)態(tài)調(diào)整容器CPU和內(nèi)存資源限制，無(wú)需重啟應(yīng)用程序

    如果您在部署Pod時(shí)指定了 CPU 和內(nèi)存資源，更改資源大小需要重新啟動(dòng) Pod。到目前為止，重啟對(duì)于正在運(yùn)行工的作負(fù)載是一種破壞性操作。 Kubernetes 1.27 中的 alpha 功能發(fā)布。其中一項(xiàng)能夠自動(dòng)調(diào)整 Pod 的 CPU 和內(nèi)存限制的大小，只需修補(bǔ)正在運(yùn)行的 Pod 定義即可更改它們，而無(wú)

    2024年02月07日
    瀏覽(29)

覺(jué)得文章有用就打賞一下文章作者

支付寶掃一掃打賞

博客贊助

微信掃一掃打賞

請(qǐng)作者喝杯咖啡吧~博客贊助

支付寶掃一掃領(lǐng)取紅包，優(yōu)惠每天領(lǐng)

二維碼1

領(lǐng)取紅包

二維碼2

領(lǐng)紅包