# 3台虚拟机 |节点|系统|IP| |-|-|-|-| |master|CentOS-8|192.168.10.90| |node1|CentOS-8|192.168.10.91| |node2|CentOS-8|192.168.10.92| # 构建基础镜像 ``` cd k8sbase vagrant box add centos8 ../vagrant_package/CentOS-8-generic.box vagrant init centos8 #启动 vagrant up #登陆系统，进行基础配置 vagrant ssh #切换到root sudo su ``` ## 基础配置 ``` #关闭防火墙 systemctl stop firewalld && systemctl disable firewalld #关闭 seLinux sed -i 's/^SELINUX=enforcing$/SELINUX=disabled/' /etc/selinux/config #关闭 swap 分区 sed -ri 's/.*swap.*/#&/' /etc/fstab #将桥接的 IPV4 流量传递到 iptables 的链 cat < /etc/sysctl.d/k8s.conf net.bridge.bridge-nf-call-ip6tables = 1 net.bridge.bridge-nf-call-iptables = 1 EOF sysctl --system #同步时间 1 date #查看时间是否正确，不正确则执行以下步骤 2 rm -rf /etc/localtime 3 ln -s /usr/share/zoneinfo/Asia/Shanghai /etc/localtime 4 设置时区 tzselect 5 同步时间 yum install -y ntpdate ntpdate cn.pool.ntp.org 6 date # yum源 vi /etc/yum.repos.d/docker-ce.repo [docker-ce-stable] name=Docker CE Stable - $basearch baseurl=https://mirrors.aliyun.com/docker-ce/linux/centos/$releasever/$basearch/stable enabled=1 gpgcheck=1 gpgkey=https://mirrors.aliyun.com/docker-ce/linux/centos/gpg vi /etc/yum.repos.d/kubernetes.repo [kubernetes] name=Kubernetes baseurl=https://mirrors.aliyun.com/kubernetes/yum/repos/kubernetes-el7-x86_64/ enabled=1 gpgcheck=1 repo_gpgcheck=1 gpgkey=https://mirrors.aliyun.com/kubernetes/yum/doc/yum-key.gpg https://mirrors.aliyun.com/kubernetes/yum/doc/rpm-package-key.gpg #安装 yum install docker-ce kubelet kubeadm kubectl systemctl enable docker systemctl enable kubelet #注意，这里我遇到一个问题，docker的驱动类型和kubelet的驱动类型不同，需要统一一下。修改docker的驱动类型为systemd cat > /etc/docker/daemon.json < --discovery-token-ca-cert-hash sha256:eb606e1c5f634d7a861fe09644dfdb12f9bfeb02534012445cc9712e4e8caede [preflight] Running pre-flight checks [WARNING FileExisting-tc]: tc not found in system path [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上看一下, 可以看见INTERNAL-IP都是我们希望的IP了（状态还是NoReady，因为网络组件还没安装) [root@master vagrant]# kubectl get nodes -o wide NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME master NotReady control-plane,master 13m v1.22.0 192.168.10.90 CentOS Linux 8 4.18.0-240.15.1.el8_3.x86_64 docker://20.10.8 node1 NotReady 8s v1.22.0 192.168.10.91 CentOS Linux 8 4.18.0-240.15.1.el8_3.x86_64 docker://20.10.8 node2 NotReady 16s v1.22.0 192.168.10.92 CentOS Linux 8 4.18.0-240.15.1.el8_3.x86_64 docker://20.10.8 ``` # node2节点除了ip,和node1节点的操作一致 # flannel网络组件在master上执行 ``` kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml #可能上面的命令因网络问题而执行失败，那就把整个库下载下来再执行 https://github.com/flannel-io/flannel #修改kube-flannel.yml，指定eth1 ... containers: - name: kube-flannel image: registry.cn-hangzhou.aliyuncs.com/google-containers/flannel:v0.9.0 command: - /opt/bin/flanneld args: - --ip-masq - --kube-subnet-mgr - --iface=eth1 ... #执行 kubectl apply -f ./Documentation/kube-flannel.yml #查询所以pod，不出所料，STATUS都是Running [root@master vagrant]# kubectl get pods -n kube-system -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES coredns-7d89d9b6b8-fcs2v 1/1 Running 0 42m 10.244.0.3 master coredns-7d89d9b6b8-kb8f8 1/1 Running 0 42m 10.244.0.2 master etcd-master 1/1 Running 1 (2m51s ago) 51m 192.168.10.90 master kube-apiserver-master 1/1 Running 2 (2m30s ago) 51m 192.168.10.90 master kube-controller-manager-master 1/1 Running 9 (45s ago) 51m 192.168.10.90 master kube-flannel-ds-4g9k2 1/1 Running 0 4m28s 192.168.10.92 node2 kube-flannel-ds-bzw9q 1/1 Running 0 5m39s 192.168.10.90 master kube-flannel-ds-c5x4l 1/1 Running 0 5m42s 192.168.10.91 node1 kube-proxy-bfl8p 1/1 Running 1 (2m8s ago) 38m 192.168.10.92 node2 kube-proxy-pf8r9 1/1 Running 1 (2m10s ago) 38m 192.168.10.91 node1 kube-proxy-vj85t 1/1 Running 1 (2m51s ago) 42m 192.168.10.90 master kube-scheduler-master 0/1 Running 4 (46s ago) 49m 192.168.10.90 master #查询所有node，不出所料，STATUS都是Ready [root@master vagrant]# kubectl get nodes -o wide NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME master Ready control-plane,master 51m v1.22.0 192.168.10.90 CentOS Linux 8 4.18.0-240.15.1.el8_3.x86_64 docker://20.10.8 node1 Ready 38m v1.22.0 192.168.10.91 CentOS Linux 8 4.18.0-240.15.1.el8_3.x86_64 docker://20.10.8 node2 Ready 38m v1.22.0 192.168.10.92 CentOS Linux 8 4.18.0-240.15.1.el8_3.x86_64 docker://20.10.8 ``` # dashboard [k8s 安装 dashboard](https://www.cuiwei.net/p/1987004779) # ingress-nginx [k8s ingress 两种部署方式nodePort和hostNetwork](http://www.cuiwei.net/p/1857935436) # 文件下载 https://github.com/chudaozhe/k8s-demo # 参考 https://developer.aliyun.com/mirror/kubernetes 1️⃣ 关于registry.aliyuncs.com/google_containers，详见 [阿里云镜像仓库市场](https://cr.console.aliyun.com/images/cn-hangzhou/google_containers/kube-apiserver/detail) # 问题 ``` # 问题1 [WARNING ImagePull]: failed to pull image registry.cn-hangzhou.aliyuncs.com/google_containers/coredns:v1.8.4: output: Error response from daemon: manifest for registry.cn-hangzhou.aliyuncs.com/google_containers/coredns:v1.8.4 not found: manifest unknown: manifest unknown # 解决办法(所以节点都需要执行) #拉取 docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/coredns:1.8.4 # 重命名 docker tag registry.cn-hangzhou.aliyuncs.com/google_containers/coredns:1.8.4 registry.cn-hangzhou.aliyuncs.com/google_containers/coredns:v1.8.4 # 删除原有镜像 docker rmi registry.cn-hangzhou.aliyuncs.com/google_containers/coredns:1.8.4 ``` 2️⃣问题2 ``` 如果kubeadm init执行失败，先确认kubelet是否正常允许 service kubelet status 如果kubelet未能正常运行，执行下面这条命令排查 journalctl -xefu kubelet 假如看到了下面这样的错误 "Failed to run kubelet" err="failed to run Kubelet: misconfiguration: kubelet cgroup driver: \"systemd\" is different from docker cgroup driver: \"cgroupfs\"" 大致意思是docker和kubelet的cgroup driver不一致 #查看docker的cgroup driver docker info #查看kubelet的cgroup driver cat /var/lib/kubelet/config.yaml #设置docker的cgroup driver为systemd cat > /etc/docker/daemon.json <

react