k8s

阿里云 Ubuntu 22.4 三节点集群部署 Kubernetes 1.33

集群信息

集群概况

节点概况

三个节点配置相同。

# 临时关闭交换空间
sudo swapoff -a
# 将
sudo sed -i '/ swap / s/^\(.*\)$/#\1/g' /etc/fstab

加载内核模块

# 临时加载模块（重启后失效）
sudo modprobe overlay
sudo modprobe br_netfilter
# 永久加载模块
sudo tee /etc/modules-load.d/k8s.conf <<EOF
overlay
br_netfilter
EOF

sudo tee /etc/sysctl.d/kubernetes.conf <<EOF
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1
net.ipv4.ip_forward = 1
EOF
sudo sysctl --system

安装容器运行时

在每个节点进行相同操作。容器运行时采用 containerd。

# 安装前置依赖
sudo apt install -y curl gnupg2 software-properties-common apt-transport-https ca-certificates

# 添加 containerd 存储库
sudo curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmour -o /etc/apt/trusted.gpg.d/containerd.gpg
sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"

# 安装 containerd
sudo apt update
sudo apt install containerd.io -y

# 
containerd config default | sudo tee /etc/containerd/config.toml >/dev/null 2>&1
sudo sed -i 's/SystemdCgroup \= false/SystemdCgroup \= true/g' /etc/containerd/config.toml

# 重启 containerd 使得更改生效
sudo systemctl restart containerd

安装 k8s

在每个节点进行相同操作。

https://kubernetes.io/zh-cn/docs/tasks/tools/install-kubectl-linux/#install-using-native-package-management

# Kubernetes 软件包在 Ubuntu 24.04 的默认包存储库中不可用，故需要添加存储库然后进行安装。
# 使用 curl 命令下载 Kubernetes 包存储库的公共签名密钥。
curl -fsSL https://pkgs.k8s.io/core:/stable:/v1.33/deb/Release.key | sudo gpg --dearmor -o /etc/apt/keyrings/kubernetes-apt-keyring.gpg

# 添加 Kubernetes apt 仓库
echo 'deb [signed-by=/etc/apt/keyrings/kubernetes-apt-keyring.gpg] https://pkgs.k8s.io/core:/stable:/v1.33/deb/ /' | sudo tee /etc/apt/sources.list.d/kubernetes.list

# 安装 kubelet kubeadm kubectl 工具
sudo apt update
sudo apt install kubelet kubeadm kubectl -y

集群初始化

主节点执行初始化

• --control-plane-endpoint为主节点IP地址

sudo kubeadm init --control-plane-endpoint=10.0.1.1

root@iZrj9976wzpibxv39zlxv3Z:~# sudo kubeadm init --control-plane-endpoint=10.0.1.1
[init] Using Kubernetes version: v1.33.3
[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 beforehand using 'kubeadm config images pull'
W0814 00:37:57.883097    7459 checks.go:846] detected that the sandbox image "registry.k8s.io/pause:3.8" of the container runtime is inconsistent with that used by kubeadm.It is recommended to use "registry.k8s.io/pause:3.10" as the CRI sandbox image.
[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 [izrj9976wzpibxv39zlxv3z kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.1.1]
[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 [izrj9976wzpibxv39zlxv3z localhost] and IPs [10.0.1.1 127.0.0.1 ::1]
[certs] Generating "etcd/peer" certificate and key
[certs] etcd/peer serving cert is signed for DNS names [izrj9976wzpibxv39zlxv3z localhost] and IPs [10.0.1.1 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 "super-admin.conf" kubeconfig file
[kubeconfig] Writing "kubelet.conf" kubeconfig file
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
[kubeconfig] Writing "scheduler.conf" kubeconfig file
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[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"
[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
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests"
[kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s
[kubelet-check] The kubelet is healthy after 501.323647ms
[control-plane-check] Waiting for healthy control plane components. This can take up to 4m0s
[control-plane-check] Checking kube-apiserver at https://10.0.1.1:6443/livez
[control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz
[control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez
[control-plane-check] kube-controller-manager is healthy after 1.634933149s
[control-plane-check] kube-scheduler is healthy after 1.931743994s
[control-plane-check] kube-apiserver is healthy after 3.500579433s
[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 izrj9976wzpibxv39zlxv3z 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 izrj9976wzpibxv39zlxv3z as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]
[bootstrap-token] Using token: jgb353.v9qxwp1uic5944zj
[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/

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 10.0.1.1:6443 --token jgb353.v9qxwp1uic5944zj \
        --discovery-token-ca-cert-hash sha256:c9a75316ca750f7e1fb350f5059d575f3c6dff85c501a256927ab681787f1b6a \
        --control-plane 

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

kubeadm join 10.0.1.1:6443 --token jgb353.v9qxwp1uic5944zj \
        --discovery-token-ca-cert-hash sha256:c9a75316ca750f7e1fb350f5059d575f3c6dff85c501a256927ab681787f1b6a

主节点

vi ~/.bashrc
export KUBECONFIG=/etc/kubernetes/admin.conf

在主节点安装网络插件（以 calico 为例）

kubectl apply -f https://docs.projectcalico.org/manifests/calico.yaml

将工作节点加入集群

每一个工作节点均需要执行一次。

root@iZrj9b9nu5j7lbkcipzqj1Z:~# kubeadm join 10.0.1.1:6443 --token jgb353.v9qxwp1uic5944zj \
        --discovery-token-ca-cert-hash sha256:c9a75316ca750f7e1fb350f5059d575f3c6dff85c501a256927ab681787f1b6a
[preflight] Running pre-flight checks
[preflight] Reading configuration from the "kubeadm-config" ConfigMap in namespace "kube-system"...
[preflight] Use 'kubeadm init phase upload-config --config your-config-file' to re-upload it.
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Starting the kubelet
[kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s
[kubelet-check] The kubelet is healthy after 1.000644935s
[kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap

This node has joined the cluster:
* Certificate signing request was sent to apiserver and a response was received.
* The Kubelet was informed of the new secure connection details.

Run 'kubectl get nodes' on the control-plane to see this node join the cluster.

在主节点获取集群各节点状态，工作节点刚加入集群处于 NotReady，约1到2分钟后会变为Ready。

kubectl get nodes

root@iZrj9976wzpibxv39zlxv3Z:~# kubectl get nodes
NAME                      STATUS     ROLES           AGE     VERSION
izrj9976wzpibxv39zlxv3z   Ready      control-plane   5m22s   v1.33.3
izrj9b9nu5j7lbkcipzqj1z   NotReady   <none>          49s     v1.33.3
izrj9hztrcp8hoxgfe9x8cz   NotReady   <none>          40s     v1.33.3

在主节点获取当前各容器状态

kubectl get pods -n kube-system

root@iZrj9976wzpibxv39zlxv3Z:~# kubectl get pods -n kube-system
NAME                                              READY   STATUS    RESTARTS   AGE
calico-kube-controllers-7498b9bb4c-289wz          1/1     Running   0          22m
calico-node-7s6sv                                 1/1     Running   0          22m
calico-node-gqttc                                 1/1     Running   0          19m
calico-node-tg9c6                                 1/1     Running   0          19m
coredns-674b8bbfcf-2kqhr                          1/1     Running   0          24m
coredns-674b8bbfcf-7k7s2                          1/1     Running   0          24m
etcd-izrj9976wzpibxv39zlxv3z                      1/1     Running   2          24m
kube-apiserver-izrj9976wzpibxv39zlxv3z            1/1     Running   2          24m
kube-controller-manager-izrj9976wzpibxv39zlxv3z   1/1     Running   2          24m
kube-proxy-8gc7r                                  1/1     Running   0          24m
kube-proxy-q4554                                  1/1     Running   0          19m
kube-proxy-r5n49                                  1/1     Running   0          19m
kube-scheduler-izrj9976wzpibxv39zlxv3z            1/1     Running   2          24m