Ubuntu20.04安裝k8s Kubernetes v1.22.1版本
- 安裝步驟
- 準備
- 環境要求
- 1.關閉swap磁區
- 2.更改net.bridge.bridge-nf-call-iptables的值為1.（Ubuntu 20.04默認為1）
- 3.安裝Docker
- 安裝k8s
- 配置源
- 添加key
- 作為節點加入集群
- 初始化
- 清空資訊:
- 問題報錯的解決
- 測驗
初始化的程序遭遇了崩潰的長久報錯,查了好多資料改了好久終于成功了!
安裝步驟
準備
環境要求
Ubuntu機器的硬體環境的要求：
cpu：2c
memory：4G/2G
軟體環境的要求：
root@node138:/etc/apt/sources.list.d# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04 LTS
Release: 20.04
Codename: focal
1.關閉swap磁區
swap磁區：交換磁區，從磁盤里分一塊空間來充當記憶體使用，性能比真正的物理記憶體要差
docker容器在記憶體里運行 --》 k8s不允許容器到swap磁區運行，要關閉swap磁區–》所以關閉swap磁區是k8s為了追求高性能
[root@kafka02 ~]# swapoff -a 臨時關閉
[root@kafka02 ~]# cat /proc/swaps
Filename Type Size Used Priority
# 永久關閉
[root@kafka02 ~]# vim /etc/fstab
注釋掉swap那一行，每臺機器都要配置
2.更改net.bridge.bridge-nf-call-iptables的值為1.（Ubuntu 20.04默認為1）
cat <<EOF | sudo tee /etc/sysctl.d/k8s.conf
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1
EOF
# 上面成功之后再輸入下面的 更新一下值
sudo sysctl --system
3.安裝Docker
Ubuntu安裝docker可以看筆者之前寫的文章！按照官方一步一步安裝的！
Ubuntu安裝Docker
安裝k8s
sudo apt install -y apt-transport-https curl
sudo apt-get install -y kubelet kubeadm kubectl
但是這樣直接安裝kubelet、kubeadm、kubectl會報如下錯（只截取一部分）
root@node138:/etc/apt# sudo apt-get install -y kubelet kubeadm kubectl
No apt package "kubeadm", but there is a snap with that name.
Try "snap install kubeadm"
所以接下來需要配置k8s相關安裝的源
配置源
修改Sources.list
可以打開 /etc/apt/sources.list 檔案，添加一行
deb https://mirrors.aliyun.com/kubernetes/apt kubernetes-xenial main
或者在/etc/apt/sources.list.d下添加一個檔案 kubernetes.list
檔案內容：
deb https://mirrors.aliyun.com/kubernetes/apt/ kubernetes-xenial main
然后執行apt-get update
執行apt-get update
如果這個時候報錯如下，說明我們沒有匯入aliyun的key
root@node138:~# apt-get update
Get:1 https://mirrors.aliyun.com/kubernetes/apt kubernetes-xenial InRelease [9,383 B]
Err:1 https://mirrors.aliyun.com/kubernetes/apt kubernetes-xenial InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY FEEA9169307EA071 NO_PUBKEY 8B57C5C2836F4BEB
接下來我們添加aliyun的key
添加key
curl https://mirrors.aliyun.com/kubernetes/apt/doc/apt-key.gpg | sudo apt-key add
root@node138:/etc/apt/sources.list.d# curl https://mirrors.aliyun.com/kubernetes/apt/doc/apt-key.gpg | sudo apt-key add
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 2537 100 2537 0 0 14836 0 --:--:-- --:--:-- --:--:-- 14836
OK
一定要記住添加了key之后重新update!!!
root@node138:/etc/apt/sources.list.d# apt-get update
Get:1 https://mirrors.aliyun.com/kubernetes/apt kubernetes-xenial InRelease [9,383 B]
Ign:2 https://mirrors.aliyun.com/kubernetes/apt kubernetes-xenial/main amd64 Packages
Get:2 https://mirrors.aliyun.com/kubernetes/apt kubernetes-xenial/main amd64 Packages [49.4 kB]
Hit:3 http://cn.archive.ubuntu.com/ubuntu focal InRelease
Hit:4 https://download.docker.com/linux/ubuntu focal InRelease
Get:5 http://cn.archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB]
Get:6 http://cn.archive.ubuntu.com/ubuntu focal-backports InRelease [101 kB]
Get:7 http://cn.archive.ubuntu.com/ubuntu focal-security InRelease [114 kB]
Get:8 http://cn.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages [1,175 kB]
Get:9 http://cn.archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages [853 kB]
Fetched 2,406 kB in 20s (120 kB/s)
Reading package lists... Done
接下來就能正常安裝了
apt-get install -y kubelet kubeadm kubectl --allow-unauthenticated
作為節點加入集群
因為筆者是利用這臺Ubuntu做node節點的,所以接下來可以直接輸入master中的命令加入集群
kubeadm join 192.168.254.129:6443 --token t5mat5.4312obzrfk4bnnu0
–discovery-token-ca-cert-hash sha256:05b0b09ce2a915ed6e3009dff885a52b95fe02359ae203a641dfcdf15819115a
注意這個token有效期只有24h喔 過期要重新新建!
kubeadm token create
root@node138:/etc/apt/sources.list.d# kubeadm join 192.168.254.129:6443 --token t5mat5.4312obzrfk4bnnu0 \
> --discovery-token-ca-cert-hash sha256:05b0b09ce2a915ed6e3009dff885a52b95fe02359ae203a641dfcdf15819115a
[preflight] Running pre-flight checks
[preflight] Reading configuration from the cluster...
[preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
[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-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.
在主master上查看 成功加入!
[root@kafka02 docker]# kubectl get nodes
NAME STATUS ROLES AGE VERSION
kafka01 Ready <none> 3h16m v1.22.1
kafka02 Ready control-plane,master 8d v1.22.1
node138 Ready <none> 49m v1.22.1
接下來擴展一下初始化做master的操作
初始化
如果和筆者一樣之前利用這臺機器部署過k8s,必須要清空資訊否則會報如下錯
root@node138:/etc/docker# sudo kubeadm init
invalid or incomplete external CA: failure loading key for apiserver: couldn't load the private key file /etc/kubernetes/pki/apiserver.key: open /etc/kubernetes/pki/apiserver.key: no such file or directory
To see the stack trace of this error execute with --v=5 or higher
清空資訊:
kubeadm reset
再重新init初始化
kubeadm init --kubernetes-version=v1.22.1 --pod-network-cidr=10.244.0.0/16
卡住一直不動
即要去拉去鏡像 但是國內鏡像下載k8s.gcr.io這種型別的鏡像然后太慢了一直卡在這一步
此命令 kubeadm config images list 獲取需要的docker鏡像名稱
kubeadm config images list
這是筆者的kubeadm版本需要的鏡像版本
root@node138:/etc/docker# kubeadm config images list
k8s.gcr.io/kube-apiserver:v1.22.1
k8s.gcr.io/kube-controller-manager:v1.22.1
k8s.gcr.io/kube-scheduler:v1.22.1
k8s.gcr.io/kube-proxy:v1.22.1
k8s.gcr.io/pause:3.5
k8s.gcr.io/etcd:3.5.0-0
k8s.gcr.io/coredns/coredns:v1.8.4
問題報錯的解決
所以我們要改阿里云的鏡像去拉去這個
kubeadm init --image-repository=registry.aliyuncs.com/google_containers --pod-network-cidr=10.244.0.0/16
然后筆者是較新版本的Kubernetes,所以當拉取阿里云的registry.aliyuncs.com/google_containers/coredns:v1.8.4這個版本的鏡像，拉取失敗就會報這個錯誤
root@node138:/etc/docker# kubeadm init --image-repository=registry.aliyuncs.com/google_containers --pod-network-cidr=10.244.0.0/16
[init] Using Kubernetes version: v1.22.1
[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 in beforehand using 'kubeadm config images pull'
error execution phase preflight: [preflight] Some fatal errors occurred:
[ERROR ImagePull]: failed to pull image registry.aliyuncs.com/google_containers/coredns:v1.8.4: output: Error response from daemon: manifest for registry.aliyuncs.com/google_containers/coredns:v1.8.4 not found: manifest unknown: manifest unknown
, error: exit status 1
[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`
To see the stack trace of this error execute with --v=5 or higher
這時候我們需要手動安裝一下
root@node138:/etc/docker# docker pull registry.aliyuncs.com/google_containers/coredns
然后修改鏡像的tag
root@node138:/etc/docker# docker tag registry.aliyuncs.com/google_containers/coredns:latest registry.aliyuncs.com/google_containers/coredns:v1.8.4
然后就可以安裝成功了!!!
以下是筆者安裝成功的樣子
按照提示做接下來要進行的操作
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config
這樣master就配置好啦,然后可以在node機器上輸入這個提示命令即可!
測驗
在master機器上輸入這條命令,可以查看子節點 (這是筆者用centos搭的master)
[root@kafka02 docker]# kubectl get nodes
NAME STATUS ROLES AGE VERSION
kafka01 Ready <none> 3h16m v1.22.1
kafka02 Ready control-plane,master 8d v1.22.1
node138 Ready <none> 49m v1.22.1
可以在master上創建pod,成功創建能 get pod 即可!
[root@kafka02 docker]# kubectl run sc-nginx --image=nginx --port=7770
pod/sc-nginx created
[root@kafka02 docker]# kubectl get pod
NAME READY STATUS RESTARTS AGE
sc-nginx 0/1 ContainerCreating 0 7s
轉載請註明出處，本文鏈接：https://www.uj5u.com/qita/298464.html
標籤：其他
上一篇：linux java -jar部署springclound 前后端分離nginx配置 Nginx區分路徑部署多個Vue專案