文档编写时间 2025/12/29,所有操作自己尝试过,放心使用
前置环境准备
服务环境选择
常见练习k8s的工具环境如下
- K3s,MicroK8s 等轻量化的k8s工具
- windows电脑上虚拟机模拟
- 买云厂商的云服务器自己搭
推荐选择3,要搞就一步到位,花点小钱,采用按量计费的话也不贵(10元即可入门)
推荐云厂商:火山引擎,便宜
服务器配置参考
2台 - 2核2g 服务器(工作节点)1台 - 2核4g 服务器(控制节点)
花销参考 0.55元/小时(2核2g 0.1元/小时,2核4g 0.35元/小时)
云服务厂商的相关配置检查
网关
所有的服务器必须在同一个可用区 安全组 中,私网必须在同一个网关中,可以登录各自服务器(像我这里的私网的网关都是在192.168.118下面的,证明没问题)
然后互相ping一下内网,看看能不能通

安全组检查
需要可以访问外网,出方向所有端口打开
因为服务全部部署在内网,所以入口方向不用配置,默认内网可以互相访问
部署详解
基础环境
1.配置hostname
shell
hostnamectl set-hostname k8s-master
hostnamectl set-hostname k8s-node1
hostnamectl set-hostname k8s-node2
// 查看hostname 命令
hostname
2.安装docker
shell
sudo yum remove docker*
sudo yum install -y yum-utils
#配置docker的yum地址
sudo yum-config-manager \
--add-repo \
http://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo
#安装指定版本
sudo yum install -y docker-ce-20.10.7 docker-ce-cli-20.10.7 containerd.io-1.4.6
#启动&开机启动docker
systemctl enable docker --now
#docker加速配置,镜像源很重要,这里设置了3个
sudo mkdir -p /etc/docker
sudo tee /etc/docker/daemon.json <<-'EOF'
{
"registry-mirrors": ["https://registry.cn-hangzhou.aliyuncs.com","https://docker.1ms.run","https://docker-0.unsee.tech"],
"exec-opts": ["native.cgroupdriver=systemd"],
"log-driver": "json-file",
"log-opts": {
"max-size": "100m"
},
"storage-driver": "overlay2"
}
EOF
sudo systemctl daemon-reload
sudo systemctl restart docker
3.k8s安装前准备
shell
# 关闭防火墙
systemctl stop firewalld
systemctl disable firewalld
# 将 SELinux 设置为 permissive 模式(相当于将其禁用)
sudo setenforce 0
sudo sed -i 's/^SELINUX=enforcing$/SELINUX=permissive/' /etc/selinux/config
# 关闭swap
swapoff -a
sed -ri 's/.*swap.*/#&/' /etc/fstab
# 允许 iptables 检查桥接流量
cat <<EOF | sudo tee /etc/modules-load.d/k8s.conf
br_netfilter
EOF
cat <<EOF | sudo tee /etc/sysctl.d/k8s.conf
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1
EOF
sudo sysctl --system
4.安装kubelet、kubeadm、kubectl
shell
#配置k8s的yum源地址
cat <<EOF | sudo tee /etc/yum.repos.d/kubernetes.repo
[kubernetes]
name=Kubernetes
baseurl=http://mirrors.aliyun.com/kubernetes/yum/repos/kubernetes-el7-x86_64
enabled=1
gpgcheck=0
repo_gpgcheck=0
gpgkey=http://mirrors.aliyun.com/kubernetes/yum/doc/yum-key.gpg
http://mirrors.aliyun.com/kubernetes/yum/doc/rpm-package-key.gpg
EOF
#安装 kubelet,kubeadm,kubectl
sudo yum install -y kubelet-1.20.9 kubeadm-1.20.9 kubectl-1.20.9
#启动kubelet
sudo systemctl enable --now kubelet
#所有机器配置master域名(替换为私网地址!)
echo "172.16.46.156 k8s-master" >> /etc/hosts
初始化master节点
执行初始化命令
shell
// 我这里用的云环境,这里只需要把apiserver的地址换成私网地址即可
kubeadm init \
--apiserver-advertise-address=172.16.46.156 \
--control-plane-endpoint=k8s-master \
--image-repository registry.cn-hangzhou.aliyuncs.com/lfy_k8s_images \
--kubernetes-version v1.20.9 \
--service-cidr=10.1.0.0/16 \
--pod-network-cidr=10.244.0.0/16
记录关键信息
记录master执行完成后的日志
shell
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/
You can now join any number of control-plane nodes by copying certificate authorities
and service account keys on each node and then running the following as root:
kubeadm join k8s-master:6443 --token en8bwp.rn3if49738aft6lb \
--discovery-token-ca-cert-hash sha256:9080d2990608eb83619a9e419360364e2c5b245d2ffedd49e0b41f2512aad367 \
--control-plane
Then you can join any number of worker nodes by running the following on each as root:
// 让从节点加入主节点的命令(保留下来)
kubeadm join k8s-master:6443 --token en8bwp.rn3if49738aft6lb \
--discovery-token-ca-cert-hash sha256:9080d2990608eb83619a9e419360364e2c5b245d2ffedd49e0b41f2512aad367
执行配置命令
shell
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config
安装Calico网络插件
这个calico插件的版本需要和k8s的版本对上,不能安装最新版本的
shell
wget https://docs.projectcalico.org/archive/v3.20/manifests/calico.yaml
kubectl apply -f calico.yaml
等待大约 1分钟左右,检查Kubernetes master运行情况:
shell
[root@localhost ~]# kubectl get node
NAME STATUS ROLES AGE VERSION
master Ready master 10m v1.19.3
安装网络插件走过的坑
如果这里显示的是NotReady
shell
[root@k8s-master ~]# kubectl get no
NAME STATUS ROLES AGE VERSION
k8s-master NotReady control-plane,master 3m5s v1.20.9
敲命令,查看详细信息
shell
// 查看系统中的所有pod
kubectl get pods -n kube-system
[root@k8s-master ~]# kubectl get pods -n kube-system
NAME READY STATUS RESTARTS AGE
calico-kube-controllers-577f77cb5c-7qcqt 0/1 Pending 0 2m31s
calico-node-tjd2p 0/1 Init:ImagePullBackOff 0 2m31s
coredns-5897cd56c4-ss4kc 0/1 Pending 0 3m52s
coredns-5897cd56c4-tlbrq 0/1 Pending 0 3m52s
etcd-k8s-master 1/1 Running 0 4m
kube-apiserver-k8s-master 1/1 Running 0 4m
kube-controller-manager-k8s-master 1/1 Running 0 4m
kube-proxy-9lqc6 1/1 Running 0 3m53s
kube-scheduler-k8s-master 1/1 Running 0 4m
发现有些READY 是0/1 说明没成功,然后看STATUS 是Init:ImagePullBackOff,说明是镜像拉取失败了,之前docker的镜像加速器有些教程用不了,不过我的文档中已经加上足够的镜像源了,不会有这个问题
也可以看看详细信息进一步确认,从Events中可以看到确实是镜像拉取失败了,重新配置下即可
shell
kubectl describe pod calico-node-tjd2p -n kube-system
~~~~~~~~
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 3m34s default-scheduler Successfully assigned kube-system/calico-node-tjd2p to k8s-master
Normal Pulling 74s (x4 over 3m34s) kubelet Pulling image "docker.io/calico/cni:v3.20.6"
Warning Failed 58s (x4 over 3m18s) kubelet Failed to pull image "docker.io/calico/cni:v3.20.6": rpc error: code = Unknown desc = Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Warning Failed 58s (x4 over 3m18s) kubelet Error: ErrImagePull
Normal BackOff 45s (x6 over 3m17s) kubelet Back-off pulling image "docker.io/calico/cni:v3.20.6"
Warning Failed 32s (x7 over 3m17s) kubelet Error: ImagePullBackOff
[root@k8s-master ~]#
workNode节点加入
在work服务器上执行
shell
// 在执行kubeadm init 的最后部分
kubeadm join k8s-master:6443 --token en8bwp.rn3if49738aft6lb \
--discovery-token-ca-cert-hash sha256:9080d2990608eb83619a9e419360364e2c5b245d2ffedd49e0b41f2512aad367
查询状态
shell
[root@k8s-master opt]# kubectl get no
NAME STATUS ROLES AGE VERSION
k8s-master Ready control-plane,master 60m v1.20.9
k8s-node1 Ready <none> 74s v1.20.9
k8s-node2 Ready <none> 61s v1.20.9
这里采用的是token,让工作节点加入集群,但是token会失效
用下面的命令,重新生成一个加入的命令即可
shell
// 生成默认的token,持续时间1天
kubeadm token create --print-join-command
// 生成时间更长的token
kubeadm token create --ttl=8760h --print-join-command