查看集群初始化所用镜像# kubeadm config images list --kubernetes-version=1.28.2# kubeadm init --kubernetes-version=1.28.2 \--apiserver-advertise-address=192.168.133.134 \--image-repository 192.168.133.128/google_containers \--service-cidr=10.96.0.0/12 \--pod-network-cidr=10.224.0.0/16 \--ignore-preflight-errors=Swap \--cri-socket=unix:///var/run/cri-dockerd.sock 执行过程[init]UsingKubernetes version: v1.28.2[preflight]Running pre-flight checks[preflight]Pulling images requiredforsetting 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 beforehandusing'kubeadm config images pull'[certs]UsingcertificateDir folder"/etc/kubernetes/pki"[certs]Generating"ca"certificate and key[certs]Generating"apiserver"certificate and key[certs]apiserver serving cert is signedforDNS names[k8s-master01 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local]and IPs[10.96.0.1 192.168.133.134][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 signedforDNS names[k8s-master01 localhost]and IPs[192.168.133.134 127.0.0.1 ::1][certs]Generating"etcd/peer"certificate and key[certs]etcd/peer serving cert is signedforDNS names[k8s-master01 localhost]and IPs[192.168.133.134 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]Usingkubeconfig 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[etcd]Creating static Pod manifestforlocal etcd in"/etc/kubernetes/manifests"[control-plane]Usingmanifest folder"/etc/kubernetes/manifests"[control-plane]Creating static Pod manifestfor"kube-apiserver"[control-plane]Creating static Pod manifestfor"kube-controller-manager"[control-plane]Creating static Pod manifestfor"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]Waitingforthe kubelet to boot up the control plane as static Podsfromdirectory"/etc/kubernetes/manifests".This can take up to 4m0s[apiclient]All control plane components are healthy after 6.001787 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 configurationforthe kubelets in the cluster[upload-certs]Skipping phase.Please see--upload-certs[mark-control-plane]Marking the node k8s-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 k8s-master01 as control-plane by adding the taints[node-role.kubernetes.io/control-plane:NoSchedule][bootstrap-token]Usingtoken: 199uo0.2lrc26dxj31sdvrw[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 orderfornodes to get long term certificate credentials[bootstrap-token]Configured RBAC rules to allow the csrapprover controller automatically approve CSRsfroma Node Bootstrap Token[bootstrap-token]Configured RBAC rules to allow certificate rotationforall 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!Tostartusingyour cluster,you need to run the following as a regular user: mkdir-p$HOME/.kube sudocp-i/etc/kubernetes/admin.conf$HOME/.kube/config sudo chown $(id-u):$(id-g)$HOME/.kube/config Alternatively,ifyou 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.133.134:6443--token 199uo0.2lrc26dxj31sdvrw \--discovery-token-ca-cert-hash sha256:cd627e4a9cdf397a74c71619df219570f3f0cb462ed32ba50f63b327d11330ae 执行以下内容# mkdir -p $HOME/.kube# sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config# sudo chown $(id -u):$(id -g) $HOME/.kube/config