在 Ubuntu 上部署 Kubernetes(k8s)时,无论是单节点测试还是生产集群,都有一些关键点和“坑”需要注意。下面按部署前 → 部署中 → 部署后 → 生产注意来梳理。
uname -a
iptables 模式)Kubernetes 不支持 Swap
sudo swapoff -a
sudo sed -i '/swap/s/^/#/' /etc/fstab
验证:
free -h
测试环境:
sudo ufw disable
生产环境需放行:
64431025030000-32767cat <<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-iptables = 1
net.bridge.bridge-nf-call-ip6tables = 1
net.ipv4.ip_forward = 1
EOF
sudo sysctl --system
K8s 已弃用 Docker(1.24+) 推荐:
安装 containerd:
sudo apt install -y containerd
sudo mkdir -p /etc/containerd
containerd config default | sudo tee /etc/containerd/config.toml
sudo systemctl restart containerd
sudo apt install -y apt-transport-https ca-certificates curl
curl -fsSL https://pkgs.k8s.io/core:/stable:/v1.29/deb/Release.key | sudo gpg --dearmor -o /etc/apt/keyrings/kubernetes-apt-keyring.gpg
echo "deb [signed-by=/etc/apt/keyrings/kubernetes-apt-keyring.gpg] https://pkgs.k8s.io/core:/stable:/v1.29/deb/ /" | sudo tee /etc/apt/sources.list.d/kubernetes.list
sudo apt update
sudo apt install -y kubelet kubeadm kubectl
sudo apt-mark hold kubelet kubeadm kubectl
sudo kubeadm init \
--pod-network-cidr=10.244.0.0/16
使用 Flannel 时必须是
10.244.0.0/16
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config
否则节点永远 NotReady
Flannel:
kubectl apply -f https://github.com/flannel-io/flannel/releases/latest/download/kube-flannel.yml
Calico(生产推荐):
kubectl apply -f https://docs.projectcalico.org/manifests/calico.yaml
Master 初始化后会输出:
kubeadm join 192.168.x.x:6443 --token xxx --discovery-token-ca-cert-hash sha256:xxx
如果忘了:
kubeadm token create --print-join-command
原因:
bridge-nf-callsudo apt install -y chrony
sudo systemctl enable --now chrony
kubelet 默认会驱逐节点:
/var/lib/kubelet/var/lib/containerd✅ 高可用:
✅ 安全:
✅ 监控:
✅ 备份:
ETCDCTL_API=3 etcdctl snapshot save snap.db
✅ Ubuntu LTS
✅ Swap off
✅ 防火墙正确
✅ containerd
✅ kubeadm/kubelet/kubectl
✅ CNI 插件
✅ 时间同步
✅ 内核参数
如果你愿意,我可以:
你现在是 学习 / 测试 / 生产 哪种场景?