本篇文章是帮助大家搭建一个本地k8s集群环境,仅供学习使用。
安装创建虚拟机
首先,我们去官网下载VMware Workstation Player,下载完成直接下一步安装就好了。安装号之后我们打开vmware,创建虚拟机。
此时需要我们提供虚拟机的镜像文件,我这里选择去下载ubuntu18.04.6的镜像,具体安装配置过程不再说明,需保证最少2G内存,2个CPU。网络选择桥接模式。
由于虚拟机自带的终端比较难用,无法复制粘贴,且安装VMware Tools老是失败,所以我推荐在主机外通过ssh的方式连接虚拟机,连接工具请自行选择。
这边我们一共创建三个虚拟机1个master,2个worker,修改三台机器/etc/hosts文件,并重复安装以下软件。
192.168.1.7 k8s-master
192.168.1.8 k8s-worker-1
192.168.1.9 k8s-worker-2
安装docker
使用官方脚本自动安装
curl -fsSL https://get.docker.com | bash -s docker --mirror Aliyun
安装完成后将当前用户添加进docker用户组,添加后退出当前用户重登即可使用docker命令
sudo usermod -aG docker ${USER}
安装kubeadm kubelet kubectl
禁用交换分区,注释swap那行
sudo vi /etc/fstab
为了让你的 Linux 节点上的 iptables 能够正确地查看桥接流量,你需要确保在你的 sysctl 配置中将 net.bridge.bridge-nf-call-iptables 设置为 1
cat <<EOF | sudo tee /etc/modules-load.d/k8s.conf
br_netfilter
EOF
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
更新 apt 包索引并安装使用 Kubernetes apt 仓库所需要的包
sudo apt-get update
sudo apt-get install -y apt-transport-https ca-certificates curl
导入apt key
curl -s https://mirrors.aliyun.com/kubernetes/apt/doc/apt-key.gpg | sudo apt-key add -
添加 Kubernetes镜像源
cat << EOF | sudo tee /etc/apt/sources.list.d/kubernetes.list
deb https://mirrors.aliyun.com/kubernetes/apt/ kubernetes-xenial main
EOF
更新 apt 包索引,安装 kubelet、kubeadm 和 kubectl
sudo apt-get update
sudo apt-get install -y kubelet kubeadm kubectl
sudo apt-mark hold kubelet kubeadm kubectl
部署k8s集群
同意kubelet和容器运行时的cgroup驱动,修改三台机器docker配置文件/etc/docker/daemon.json
{
"exec-opts": [
"native.cgroupdriver=systemd"
]
}
重启docker
systemctl restart docker
然后master上运行kubeadm
sudo kubeadm init --apiserver-advertise-address=192.168.1.7
报错,因为有墙的原因
error execution phase preflight: [preflight] Some fatal errors occurred:
[ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-apiserver:v1.23.1: output: Error response from daemon: Get "https://k8s.gcr.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
, error: exit status 1
[ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-controller-manager:v1.23.1: output: Error response from daemon: Get "https://k8s.gcr.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
, error: exit status 1
[ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-scheduler:v1.23.1: output: Error response from daemon: Get "https://k8s.gcr.io/v2/": context deadline exceeded
, error: exit status 1
[ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-proxy:v1.23.1: output: Error response from daemon: Get "https://k8s.gcr.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
, error: exit status 1
[ERROR ImagePull]: failed to pull image k8s.gcr.io/pause:3.6: output: Error response from daemon: Get "https://k8s.gcr.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
, error: exit status 1
[ERROR ImagePull]: failed to pull image k8s.gcr.io/etcd:3.5.1-0: output: Error response from daemon: Get "https://k8s.gcr.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
, error: exit status 1
[ERROR ImagePull]: failed to pull image k8s.gcr.io/coredns/coredns:v1.8.6: output: Error response from daemon: Get "https://k8s.gcr.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
, error: exit status 1
通过以下命令拉去镜像
kubeadm config images pull --image-repository=registry.aliyuncs.com/google_containers
然后tag 成报错的镜像名
docker image tag registry.aliyuncs.com/google_containers/kube-apiserver:v1.23.1 k8s.gcr.io/kube-apiserver:v1.23.1
docker image tag registry.aliyuncs.com/google_containers/kube-proxy:v1.23.1 k8s.gcr.io/kube-proxy:v1.23.1
docker image tag registry.aliyuncs.com/google_containers/kube-scheduler:v1.23.1 k8s.gcr.io/kube-scheduler:v1.23.1
docker image tag registry.aliyuncs.com/google_containers/kube-controller-manager:v1.23.1 k8s.gcr.io/kube-controller-manager:v1.23.1
docker image tag registry.aliyuncs.com/google_containers/etcd:3.5.1-0 k8s.gcr.io/etcd:3.5.1-0
docker image tag registry.aliyuncs.com/google_containers/coredns:v1.8.6 k8s.gcr.io/coredns/coredns:v1.8.6
docker image tag registry.aliyuncs.com/google_containers/pause:3.6 k8s.gcr.io/pause:3.6
然后再次执行
sudo kubeadm init --apiserver-advertise-address=192.168.1.7 --pod-network-cidr 10.244.0.0/16
分别去其他的两个worker node上执行以下命令
sudo kubeadm join 192.168.1.7:6443 --token zecqoe.e8knd3egtua3zxgw --discovery-token-ca-cert-hash sha256:b6121573b2c98d864d6ec7ad5429602e23abfaa771949cf61568223d87ac1337
有些k8s.gcr.io的image下载不下来,将k8s.gcr.io改成registry.aliyuncs.com/google_containers去pull image,然后再tag成需要的镜像名即可。
接着安装cni插件,复制该文件内容到本地文件kube-flannel.yaml https://github.com/flannel-io/flannel/blob/v0.16.0/Documentation/kube-flannel.yml,然后执行
kubectl apply -f kube-flannel.yaml
由于我执行kubeadm init的时候没有添加--pod-network-cidr,所以需要执行这篇文章步骤https://blog.csdn.net/qq_36713450/article/details/109524817
到这里,一个简单的集群就运行起来了
固定IP
为了防止各个节点的ip地址变化,需设置固定IP
查看gateway,执行以下命令Destination是0.0.0.0的那行gateway即是
netstat -rn
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 enp0s3
查看dns, 执行以下命令后的nameserver既是
more /etc/resolv.conf
然后修改/etc/netplan/00-installer-config.yaml
修改前
# This is the network config written by 'subiquity'
network:
ethernets:
enp0s3:
dhcp4: true
version: 2
修改后
# This is the network config written by 'subiquity'
network:
ethernets:
enp0s3:
dhcp4: no
addresses: [192.168.1.8/24] #设置本机IP及掩码,/24即表示24位掩码255.255.255.0
gateway4: 192.168.1.1 #gateway
nameservers:
addresses: [127.0.0.53] #dns
version: 2