K8s安装-kubeadm、kubelet 和 kubectl（二）

 安装 kubeadm、kubelet 和 kubectl

你需要在每台虚拟机上安装以下的软件包

• kubeadm：用来初始化集群的指令。

• kubelet：在集群中的每个节点上用来启动 Pod 和容器等。

• kubectl：用来与集群通信的命令行工具。

配置yum源

使用yum安装，为了加快速度，这里使用阿里云作为源地址。

cat <<EOF | sudo tee /etc/yum.repos.d/kubernetes.repo
[kubernetes]
name=Kubernetes
baseurl=https://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 
exclude=kubelet kubeadm kubectl
EOF

执行安装命令

sudo yum -y install kubeadm-1.25.4 kubelet-1.25.4 kubectl-1.25.4 --disableexcludes=kubernetes

设置kubelet为systemctl启动

sudo systemctl enable --now kubelet

kubelet 现在每隔几秒就会重启，因为它陷入了一个等待 kubeadm 指令的死循环。

kubeadm 创建集群

准备所需的容器镜像（推荐）

这个步骤是可选的，只适用于你希望 kubeadm init 和 kubeadm join 不去下载存放在 registry.k8s.io 上的默认的容器镜像的情况

因国内网络访问国外拉去镜像过慢或者直接超时，推荐预拉取Kubeadm初始化命令所需的镜像。

执行命令查看需预加载的镜像

kubeadm config images list

结果如下

• master节点

我们这边直接从阿里云拉去镜像，

crictl pull registry.cn-hangzhou.aliyuncs.com/google_containers/kube-apiserver:v1.25.4
crictl pull registry.cn-hangzhou.aliyuncs.com/google_containers/kube-controller-manager:v1.25.4
crictl pull registry.cn-hangzhou.aliyuncs.com/google_containers/kube-scheduler:v1.25.4
crictl pull registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy:v1.25.4
crictl pull registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.8
crictl pull registry.cn-hangzhou.aliyuncs.com/google_containers/etcd:3.5.5-0
crictl pull registry.cn-hangzhou.aliyuncs.com/google_containers/coredns:v1.9.3

 为了初始化时能被registry.k8s.io命名空间识别，给这些下载的镜像打标签。命令如下

ctr -n k8s.io i tag registry.cn-hangzhou.aliyuncs.com/google_containers/kube-apiserver:v1.25.4 k8s.gcr.io/kube-apiserver:v1.25.4
ctr -n k8s.io i tag registry.cn-hangzhou.aliyuncs.com/google_containers/kube-controller-manager:v1.25.4 k8s.gcr.io/kube-controller-manager:v1.25.4
ctr -n k8s.io i tag registry.cn-hangzhou.aliyuncs.com/google_containers/kube-scheduler:v1.25.4 k8s.gcr.io/kube-scheduler:v1.25.4
ctr -n k8s.io i tag registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy:v1.25.4 k8s.gcr.io/kube-proxy:v1.25.4
ctr -n k8s.io i tag registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.8 k8s.gcr.io/pause:3.8
ctr -n k8s.io i tag registry.cn-hangzhou.aliyuncs.com/google_containers/etcd:3.5.5-0 k8s.gcr.io/etcd:3.5.5-0
ctr -n k8s.io i tag registry.cn-hangzhou.aliyuncs.com/google_containers/coredns:v1.9.3 k8s.gcr.io/coredns/coredns:v1.9.3

• node节点

子节点不需要那么多镜像，只需kube-proxy和pause镜像。

阿里云拉去镜像

crictl pull registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy:v1.25.4
crictl pull registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.8

镜像打标签

ctr -n k8s.io i tag registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy:v1.25.4 k8s.gcr.io/kube-proxy:v1.25.4
ctr -n k8s.io i tag registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.8 k8s.gcr.io/pause:3.8

kubeadm初始化

• 初始化参数

初始化只需在master节点主机上执行。打印初始化参数 

kubeadm config print init-defaults > init.yaml

修改默认参数，我这边配置如下

apiVersion: kubeadm.k8s.io/v1beta3
bootstrapTokens:
- groups:
  - system:bootstrappers:kubeadm:default-node-token
  token: abcdef.0123456789abcdef
  ttl: 24h0m0s
  usages:
  - signing
  - authentication
kind: InitConfiguration
localAPIEndpoint:
  advertiseAddress: 192.168.24.135
  bindPort: 6443
nodeRegistration:
  criSocket: unix:///var/run/containerd/containerd.sock
  imagePullPolicy: IfNotPresent
  name: master
  taints: null
---
apiServer:
  timeoutForControlPlane: 4m0s
apiVersion: kubeadm.k8s.io/v1beta3
certificatesDir: /etc/kubernetes/pki
clusterName: kubernetes
controllerManager: {}
dns: {}
etcd:
  local:
    dataDir: /var/lib/etcd
imageRepository: registry.cn-hangzhou.aliyuncs.com/google_containers
kind: ClusterConfiguration
kubernetesVersion: 1.25.0
networking:
  dnsDomain: cluster.local
  serviceSubnet: 10.96.0.0/12
  podSubnet: 192.168.0.0/16
scheduler: {}

这里主要修改podSubnet、advertiseAddress、imageRepository，其他根据实际情况修改。

• 执行初始化

执行并打印初始化日志，命令如下

kubeadm init --config init.yaml > kubeadm-init.log

也可使用

kubeadm init --kubernetes-version=v1.25.4 --pod-network-cidr=10.244.0.0/16 --apiserver-advertise-address=192.168.24.135 --image-repository=registry.cn-hangzhou.aliyuncs.com/google_containers

执行成功后，打印如下日志

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/

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

kubeadm join 192.168.24.135:6443 --token abcdef.0123456789abcdef \
    --discovery-token-ca-cert-hash sha256:97056c4a02872fb494889e53c74e9f0c559c137545a97662ec1bac5a256736a0 

为了保证可以正常使用集群，普通用户需执行如下命令

mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config

如果你使用的账号是root，还可以执行下面命令，和上面的效果是一样的

export KUBECONFIG=/etc/kubernetes/admin.conf