ASCII码 ASCII码

最新的 k8s v1.23.5安装

发布于：2022-04-30 22:25:13  栏目：技术文档

镜像下载、域名解析、时间同步请点击 阿里云开源镜像站

一、在两台机器上安装docker

  1. // 1.安装Docker源
  2. yum install -y wget && wget https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo -O /etc/yum.repos.d/docker-ce.repo
  4. // 2.安装Docker
  5. yum -y install docker-ce-18.06.1.ce-3.el7
  7. // 3.开启自启和启动
  8. systemctl enable docker && systemctl start docker
  10. // 4.查看版本
  11. docker --version

二、安装最新的，k8s

  1. // 查找最新版本
  2. [root@master ~]# curl -sSL https://dl.k8s.io/release/stable.txt
  3. v1.23.5
  4. // 下载安装
  5. [root@master tmp]# wget -q https://dl.k8s.io/v1.23.5/kubernetes-server-linux-amd64.tar.gz
  7. [root@master tmp]# tar -zxf kubernetes-server-linux-amd64.tar.gz
  8. [root@master tmp]# ls kubernetes
  9. addons  kubernetes-src.tar.gz  LICENSES  server
  10. [root@master tmp]# ls kubernetes/server/bin/ | grep -E 'kubeadm|kubelet|kubectl'
  11. kubeadm
  12. kubectl
  13. kubelet
  15. // 可以看到在 server/bin/ 目录下有我们所需要的全部内容，将我们所需要的 kubeadm kubectl kubelet 等都移动至 /usr/bin 目录下。
  16. [root@master tmp]# mv kubernetes/server/bin/kube{adm,ctl,let} /usr/bin/
  17. [root@master tmp]# ls /usr/bin/kube*
  18. /usr/bin/kubeadm  /usr/bin/kubectl  /usr/bin/kubelet
  19. [root@master tmp]# kubeadm version
  20. [root@master tmp]# kubectl version --client
  21. [root@master tmp]# kubelet --version
  23. //为了在生产环境中保障各组件的稳定运行，同时也为了便于管理，我们增加对 kubelet 的 systemd 的配置，由 systemd 对服务进行管理。
  25. [root@master tmp]# cat <<'EOF' > /etc/systemd/system/kubelet.service
  26. [Unit]
  27. Description=kubelet: The Kubernetes Agent
  28. Documentation=http://kubernetes.io/docs/
  30. [Service]
  31. ExecStart=/usr/bin/kubelet
  32. Restart=always
  33. StartLimitInterval=0
  34. RestartSec=10
  36. [Install]
  37. WantedBy=multi-user.target
  38. EOF
  39. [root@master tmp]# mkdir -p /etc/systemd/system/kubelet.service.d
  40. [root@master tmp]# cat <<'EOF' > /etc/systemd/system/kubelet.service.d/kubeadm.conf
  41. [Service]
  42. Environment="KUBELET_KUBECONFIG_ARGS=--bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf"
  43. Environment="KUBELET_CONFIG_ARGS=--config=/var/lib/kubelet/config.yaml"
  44. EnvironmentFile=-/var/lib/kubelet/kubeadm-flags.env
  45. EnvironmentFile=-/etc/default/kubelet
  46. ExecStart=
  47. ExecStart=/usr/bin/kubelet $KUBELET_KUBECONFIG_ARGS $KUBELET_CONFIG_ARGS $KUBELET_KUBEADM_ARGS $KUBELET_EXTRA_ARGS
  48. EOF
  49. // 设置开机自启
  50. [root@master tmp]# systemctl enable kubelet
  51. Created symlink from /etc/systemd/system/multi-user.target.wants/kubelet.service to /etc/systemd/system/kubelet.service.
  54. // 此时，我们的前期准备已经基本完成，可以使用 kubeadm 来创建集群了。别着急，在此之前，我们还需要安装两个工具，名为crictl 和 socat。
  56. // Kubernetes v1.23.5 对应 crictl-v1.23.0
  57. [root@master ~]# wget https://github.com/kubernetes-sigs/cri-tools/releases/download/v1.23.0/crictl-v1.23.0-linux-amd64.tar.gz
  59. [root@master ~]# tar zxvf crictl-v1.23.0-linux-amd64.tar.gz
  60. [root@master ~]# mv crictl /usr/bin/
  62. sudo yum install -y socat
  63. // 启动 master
  64. [root@master ~]# kubeadm init --image-repository registry.aliyuncs.com/google_containers --pod-network-cidr=10.244.0.0/16
  65. [init] Using Kubernetes version: v1.23.5
  66. [preflight] Running pre-flight checks
  67. error execution phase preflight: [preflight] Some fatal errors occurred:
  68.         [ERROR FileExisting-conntrack]: conntrack not found in system path
  69. [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`
  70. To see the stack trace of this error execute with --v=5 or higher
  72. // 报错了 需要安装conntrack-tools
  73. yum -y install socat conntrack-tools
  75. // 又报错了
  76. [kubelet-check] Initial timeout of 40s passed.
  77. [kubelet-check] It seems like the kubelet isn't running or healthy.
  78. [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp [::1]:10248: connect: connection refused.
  80. // Docker是用yum安装的，docker的cgroup驱动程序默认设置为systemd。默认情况下Kubernetes cgroup为system，我们需要更改Docker cgroup驱动，
  81. # 添加以下内容
  82. vim /etc/docker/daemon.json
  83. {
  84.   "exec-opts": ["native.cgroupdriver=systemd"]
  85. }
  87. # 重启docker
  88. systemctl restart docker
  89. # 重新初始化 kubeadm 
  90. kubeadm reset # 先重置
  92. kubeadm init \
  93. --apiserver-advertise-address=192.168.42.122  \
  94. --image-repository registry.aliyuncs.com/google_containers \
  95. --kubernetes-version v1.22.2 \
  96. --service-cidr=10.96.0.0/12 \
  97. --pod-network-cidr=10.244.0.0/16 \
  98. --ignore-preflight-errors=all
  101. kubeadm reset
  103. // 可以简单初始化
  104. kubeadm init --image-repository registry.aliyuncs.com/google_containers --pod-network-cidr=10.244.0.0/16
  106. Your Kubernetes control-plane has initialized successfully!
  109. /var/lib/kubelet/config.yaml   #kubeadm配置文件
  110. /etc/kubernetes/pki            #证书存放目录
  113. [root@master ~]# kubeadm config images list --kubernetes-version v1.23.5
  114. k8s.gcr.io/kube-apiserver:v1.23.5
  115. k8s.gcr.io/kube-controller-manager:v1.23.5
  116. k8s.gcr.io/kube-scheduler:v1.23.5
  117. k8s.gcr.io/kube-proxy:v1.23.5
  118. k8s.gcr.io/pause:3.6
  119. k8s.gcr.io/etcd:3.5.1-0
  120. k8s.gcr.io/coredns/coredns:v1.8.6
  121. [root@master ~]# kubeadm config images pull --image-repository registry.aliyuncs.com/google_containers --kubernetes-version v1.23.5
  122. [config/images] Pulled registry.aliyuncs.com/google_containers/kube-apiserver:v1.23.5
  123. [config/images] Pulled registry.aliyuncs.com/google_containers/kube-controller-manager:v1.23.5
  124. [config/images] Pulled registry.aliyuncs.com/google_containers/kube-scheduler:v1.23.5
  125. [config/images] Pulled registry.aliyuncs.com/google_containers/kube-proxy:v1.23.5
  126. [config/images] Pulled registry.aliyuncs.com/google_containers/pause:3.6
  127. [config/images] Pulled registry.aliyuncs.com/google_containers/etcd:3.5.1-0
  128. [config/images] Pulled registry.aliyuncs.com/google_containers/coredns:v1.8.6
  130. // 配置 环境变量 ，每次重启，kubeadm 都要配置，这个待研究
  131.   mkdir -p $HOME/.kube
  132.   sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
  133.   sudo chown $(id -u):$(id -g) $HOME/.kube/config
  135. Alternatively, if you are the root user, you can run:
  136.   export KUBECONFIG=/etc/kubernetes/admin.conf
  138. You should now deploy a pod network to the cluster.
  139. Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at:
  140.   https://kubernetes.io/docs/concepts/cluster-administration/addons/
  142. Then you can join any number of worker nodes by running the following on each as root:
  144. // 安装 通信组件 flannel 或者 calico
  146. mkdir ~/kubernetes-flannel && cd ~/kubernetes-flannel
  148. wget https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml
  150. kubectl apply -f kube-flannel.yml
  153. kubectl get nodes
  155. [root@master ~]# kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml
  156. Warning: policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
  157. podsecuritypolicy.policy/psp.flannel.unprivileged created
  158. clusterrole.rbac.authorization.k8s.io/flannel created
  159. clusterrolebinding.rbac.authorization.k8s.io/flannel created
  160. serviceaccount/flannel created
  161. configmap/kube-flannel-cfg created
  162. daemonset.apps/kube-flannel-ds created
  163. [root@master ~]# kubectl get pod -n kube-system
  164. NAME                             READY   STATUS    RESTARTS   AGE
  165. coredns-6d8c4cb4d-7jfb8          0/1     Pending   0          11m
  166. coredns-6d8c4cb4d-m8hfd          0/1     Pending   0          11m
  167. etcd-master                      1/1     Running   4          11m
  168. kube-apiserver-master            1/1     Running   3          11m
  169. kube-controller-manager-master   1/1     Running   4          11m
  170. kube-flannel-ds-m65q6            1/1     Running   0          17s
  171. kube-proxy-qlrmp                 1/1     Running   0          11m
  172. kube-scheduler-master            1/1     Running   4          11m
  173. // coredns 一直是 Pending没有找到原因
  174. // 于是乎决定换成 calico试试
  176. 先删除  kube-flannel
  178. [root@master ~]# kubectl delete -f kube-flannel.yml
  179. Warning: policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
  180. podsecuritypolicy.policy "psp.flannel.unprivileged" deleted
  181. clusterrole.rbac.authorization.k8s.io "flannel" deleted
  182. clusterrolebinding.rbac.authorization.k8s.io "flannel" deleted
  183. serviceaccount "flannel" deleted
  184. configmap "kube-flannel-cfg" deleted
  185. daemonset.apps "kube-flannel-ds" deleted
  187. [root@master ~]# ifconfig cni0 down
  188. cni0: ERROR while getting interface flags: No such device
  189. [root@master ~]# ip link delete cni0
  190. Cannot find device "cni0"
  191. [root@master ~]# rm -rf /var/lib/cni/
  192. [root@master ~]# ifconfig flannel.1 down
  193. [root@master ~]# ip link delete flannel.1
  194. [root@master ~]# rm -f /etc/cni/net.d/*
  195. [root@master ~]# restart kubelet
  196. -bash: restart: command not found
  197. [root@master ~]# systemctl restart kubelet
  198. // 安装 calico 
  199. [root@master ~]# curl https://projectcalico.docs.tigera.io/manifests/calico.yaml -O
  200.   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
  201.                                  Dload  Upload   Total   Spent    Left  Speed
  202. 100  212k  100  212k    0     0  68018      0  0:00:03  0:00:03 --:--:-- 68039
  203. [root@master ~]# ls
  204. calico.yaml  kube-flannel.yml  kubernetes-flannel
  205. [root@master ~]# kubectl get nodes
  206. NAME     STATUS     ROLES                  AGE   VERSION
  207. master   NotReady   control-plane,master   16h   v1.23.5
  208. node1    NotReady   <none>                 12h   v1.23.5
  209. [root@master ~]# kubectl apply -f calico.yaml 
  210. configmap/calico-config created
  211. customresourcedefinition.apiextensions.k8s.io/bgpconfigurations.crd.projectcalico.org created
  212. customresourcedefinition.apiextensions.k8s.io/bgppeers.crd.projectcalico.org created
  213. customresourcedefinition.apiextensions.k8s.io/blockaffinities.crd.projectcalico.org created
  214. customresourcedefinition.apiextensions.k8s.io/caliconodestatuses.crd.projectcalico.org created
  215. customresourcedefinition.apiextensions.k8s.io/clusterinformations.crd.projectcalico.org created
  216. customresourcedefinition.apiextensions.k8s.io/felixconfigurations.crd.projectcalico.org created
  217. customresourcedefinition.apiextensions.k8s.io/globalnetworkpolicies.crd.projectcalico.org created
  218. customresourcedefinition.apiextensions.k8s.io/globalnetworksets.crd.projectcalico.org created
  219. customresourcedefinition.apiextensions.k8s.io/hostendpoints.crd.projectcalico.org created
  220. customresourcedefinition.apiextensions.k8s.io/ipamblocks.crd.projectcalico.org created
  221. customresourcedefinition.apiextensions.k8s.io/ipamconfigs.crd.projectcalico.org created
  222. customresourcedefinition.apiextensions.k8s.io/ipamhandles.crd.projectcalico.org created
  223. customresourcedefinition.apiextensions.k8s.io/ippools.crd.projectcalico.org created
  224. customresourcedefinition.apiextensions.k8s.io/ipreservations.crd.projectcalico.org created
  225. customresourcedefinition.apiextensions.k8s.io/kubecontrollersconfigurations.crd.projectcalico.org created
  226. customresourcedefinition.apiextensions.k8s.io/networkpolicies.crd.projectcalico.org created
  227. customresourcedefinition.apiextensions.k8s.io/networksets.crd.projectcalico.org created
  228. clusterrole.rbac.authorization.k8s.io/calico-kube-controllers created
  229. clusterrolebinding.rbac.authorization.k8s.io/calico-kube-controllers created
  230. clusterrole.rbac.authorization.k8s.io/calico-node created
  231. clusterrolebinding.rbac.authorization.k8s.io/calico-node created
  232. daemonset.apps/calico-node created
  233. serviceaccount/calico-node created
  234. deployment.apps/calico-kube-controllers created
  235. serviceaccount/calico-kube-controllers created
  236. Warning: policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget
  237. poddisruptionbudget.policy/calico-kube-controllers created
  238. // 查询 pod
  239. [root@master ~]# kubectl get -w pod -A
  240. NAMESPACE     NAME                                       READY   STATUS    RESTARTS   AGE
  241. kube-system   calico-kube-controllers-56fcbf9d6b-28w9g   1/1     Running   0          21m
  242. kube-system   calico-node-btgnl                          1/1     Running   0          21m
  243. kube-system   calico-node-z64mb                          1/1     Running   0          21m
  244. kube-system   coredns-6d8c4cb4d-8pnxx                    1/1     Running   0          12h
  245. kube-system   coredns-6d8c4cb4d-jdbj2                    1/1     Running   0          12h
  246. kube-system   etcd-master                                1/1     Running   4          17h
  247. kube-system   kube-apiserver-master                      1/1     Running   3          17h
  248. kube-system   kube-controller-manager-master             1/1     Running   4          17h
  249. kube-system   kube-proxy-68qrn                           1/1     Running   0          12h
  250. kube-system   kube-proxy-qlrmp                           1/1     Running   0          17h
  251. kube-system   kube-scheduler-master                      1/1     Running   4          17h
  252. 运行正常了

原文链接：https://blog.csdn.net/qq_36002737/article/details/123678418

相关推荐
阅读 +

© 2020 asciim码

人生就是一场修行