Kubeadm 部署k8s集群

网友投稿 217 2022-09-12

Kubeadm 部署k8s集群

@[toc]

一.环境准备

master(2C/4G,cpu核心数要求大于2) 192.168.19.10 docker、kubeadm、kubelet、kubectl、flannel node01(2C/2G) 192.168.19.11 docker、kubeadm、kubelet、kubectl、flannel node02(2C/2G) 192.168.19.17 docker、kubeadm、kubelet、kubectl、flannel Harbor节点(hub.kgc.com) 192.168.19.18 docker、docker-compose、harbor-offline-v1.2.2

1.在所有节点上安装Docker和kubeadm2.部署Kubernetes Master3.部署容器网络插件4.部署 Kubernetes Node,将节点加入Kubernetes集群中5.部署 Dashboard Web 页面,可视化查看Kubernetes资源6.部署 Harbor 私有仓库,存放镜像资源

//所有节点,关闭防火墙规则,关闭selinux,关闭swap交换 systemctl stop firewalld systemctl disable firewalld setenforce 0 iptables -F swapoff -a #交换分区必须要关闭 #加载 ip_vs 模块 for i in $(ls /usr/lib/modules/$(uname -r)/kernel/net/netfilter/ipvs|grep -o "^[^.]*");do echo $i; /sbin/modinfo -F filename $i >/dev/null 2>&1 && /sbin/modprobe $i;done //修改主机名 hostnamectl set-hostname master hostnamectl set-hostname node01 hostnamectl set-hostname node02 //所有节点修改hosts文件 vim /etc/hosts 192.168.19.10 master1 192.168.19.11 node1 192.168.19.17 node2 //调整内核参数 cat > /etc/sysctl.d/kubernetes.conf << EOF net.bridge.bridge-nf-call-ip6tables=1 #开启网桥模式,可将网桥的流量传递给iptables链 net.bridge.bridge-nf-call-iptables=1 net.ipv6.conf.all.disable_ipv6=1 #关闭ipv6协议 net.ipv4.ip_forward=1 EOF //生效参数 sysctl --system

二.所有节点安装docker

-------------------- 所有节点安装docker -------------------- 如果之前配置的是本地源 那么就把配置的本地源文件拖出来重新更新yum缓存 cd /etc/yum.repos.d/repo.bak/ mv *.repo /etc/yum.repos.d/ yum clean all && yum makecache yum install -y yum-utils device-mapper-persistent-data lvm2 yum-config-manager --add-repo yum install -y docker-ce docker-ce-cli containerd.io mkdir /etc/docker cat > /etc/docker/daemon.json <

==注,安装docker就不演示了==

三.所有节点安装kubeadm,kubelet和kubectl

//定义kubernetes源 cat > /etc/yum.repos.d/kubernetes.repo << EOF [kubernetes] name=Kubernetes baseurl=https://mirrors.aliyun.com/kubernetes/yum/repos/kubernetes-el7-x86_64 enabled=1 gpgcheck=0 repo_gpgcheck=0 gpgkey=https://mirrors.aliyun.com/kubernetes/yum/doc/rpm-package-key.gpg EOF yum install -y kubelet-1.20.11 kubeadm-1.20.11 kubectl-1.20.11 //开机自启kubelet systemctl enable kubelet.service #K8S通过kubeadm安装出来以后都是以Pod方式存在,即底层是以容器方式运行,所以kubelet必须设置开机自启

四.部署K8S集群

//查看初始化需要的镜像 kubeadm config images list //在 master 节点上传 v1.20.11.zip 压缩包至 /opt 目录 unzip v1.20.11.zip -d /opt/k8s cd /opt/k8s/v1.20.11 for i in $(ls *.tar); do docker load -i $i; done //复制镜像和脚本到 node 节点,并在 node 节点上执行脚本加载镜像文件 scp -r /opt/k8s root@node01:/opt scp -r /opt/k8s root@node02:/opt //初始化kubeadm 方法一: kubeadm config print init-defaults > /opt/kubeadm-config.yaml cd /opt/ vim kubeadm-config.yaml ...... 11 localAPIEndpoint: 12 advertiseAddress: 192.168.80.10 #指定master节点的IP地址 13 bindPort: 6443 ...... 34 kubernetesVersion: v1.20.11 #指定kubernetes版本号 35 networking: 36 dnsDomain: cluster.local 37 podSubnet: "10.244.0.0/16" #指定pod网段,10.244.0.0/16用于匹配flannel默认网段 38 serviceSubnet: 10.96.0.0/16 #指定service网段 39 scheduler: {} #末尾再添加以下内容 --- apiVersion: kubeproxy.config.k8s.io/v1alpha1 kind: KubeProxyConfiguration mode: ipvs #把默认的kube-proxy调度方式改为ipvs模式 kubeadm init --config=kubeadm-config.yaml --upload-certs | tee kubeadm-init.log #--experimental-upload-certs 参数可以在后续执行加入节点时自动分发证书文件,k8sV1.16版本开始替换为 --upload-certs #tee kubeadm-init.log 用以输出日志 //查看 kubeadm-init 日志 less kubeadm-init.log //kubernetes配置文件目录 ls /etc/kubernetes/ //存放ca等证书和密码的目录 ls /etc/kubernetes/pki 方法二: kubeadm init \ --apiserver-advertise-address=192.168.80.10 \ --image-repository registry.aliyuncs.com/google_containers \ --kubernetes-version=v1.20.11 \ --service-cidr=10.96.0.0/16 \ --pod-network-cidr=10.244.0.0/16 \ --token-ttl=0 -------------------------------------------------------------------------------------------- 初始化集群需使用kubeadm init命令,可以指定具体参数初始化,也可以指定配置文件初始化。 可选参数: --apiserver-advertise-address:apiserver通告给其他组件的IP地址,一般应该为Master节点的用于集群内部通信的IP地址,0.0.0.0表示节点上所有可用地址 --apiserver-bind-port:apiserver的监听端口,默认是6443 --cert-dir:通讯的ssl证书文件,默认/etc/kubernetes/pki --control-plane-endpoint:控制台平面的共享终端,可以是负载均衡的ip地址或者dns域名,高可用集群时需要添加 --image-repository:拉取镜像的镜像仓库,默认是k8s.gcr.io --kubernetes-version:指定kubernetes版本 --pod-network-cidr:pod资源的网段,需与pod网络插件的值设置一致。通常,Flannel网络插件的默认为10.244.0.0/16,Calico插件的默认值为192.168.0.0/16; --service-cidr:service资源的网段 --service-dns-domain:service全域名的后缀,默认是cluster.local --------------------------------------------------------------------------------------------- 方法二初始化后需要修改 kube-proxy 的 configmap,开启 ipvs kubectl edit cm kube-proxy -n=kube-system 修改mode: ipvs 提示: ...... 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 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.80.10:6443 --token rc0kfs.a1sfe3gl4dvopck5 \ --discovery-token-ca-cert-hash sha256:864fe553c812df2af262b406b707db68b0fd450dc08b34efb73dd5a4771d37a2 //设定kubectl kubectl需经由API server认证及授权后方能执行相应的管理操作,kubeadm 部署的集群为其生成了一个具有管理员权限的认证配置文件 /etc/kubernetes/admin.conf,它可由 kubectl 通过默认的 “$HOME/.kube/config” 的路径进行加载。 mkdir -p $HOME/.kube cp -i /etc/kubernetes/admin.conf $HOME/.kube/config chown $(id -u):$(id -g) $HOME/.kube/config //如果 kubectl get cs 发现集群不健康,更改以下两个文件 vim /etc/kubernetes/manifests/kube-scheduler.yaml vim /etc/kubernetes/manifests/kube-controller-manager.yaml # 修改如下内容 把--bind-address=127.0.0.1变成--bind-address=192.168.80.10 #修改成k8s的控制节点master01的ip 把httpGet:字段下的hosts由127.0.0.1变成192.168.80.10(有两处) #- --port=0 # 搜索port=0,把这一行注释掉 systemctl restart kubelet //所有节点部署网络插件flannel 方法一: //所有节点上传flannel镜像 flannel.tar 到 /opt 目录,master节点上传 kube-flannel.yml 文件 cd /opt docker load < flannel.tar //在 master 节点创建 flannel 资源 kubectl apply -f kube-flannel.yml 方法二: kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml //在 node 节点上执行 kubeadm join 命令加入群集 kubeadm join 192.168.80.10:6443 --token rc0kfs.a1sfe3gl4dvopck5 \ --discovery-token-ca-cert-hash sha256:864fe553c812df2af262b406b707db68b0fd450dc08b34efb73dd5a4771d37a2 //在master节点查看节点状态 kubectl get nodes kubectl get pods -n kube-system NAME READY STATUS RESTARTS AGE coredns-bccdc95cf-c9w6l 1/1 Running 0 71m coredns-bccdc95cf-nql5j 1/1 Running 0 71m etcd-master 1/1 Running 0 71m kube-apiserver-master 1/1 Running 0 70m kube-controller-manager-master 1/1 Running 0 70m kube-flannel-ds-amd64-kfhwf 1/1 Running 0 2m53s kube-flannel-ds-amd64-qkdfh 1/1 Running 0 46m kube-flannel-ds-amd64-vffxv 1/1 Running 0 2m56s kube-proxy-558p8 1/1 Running 0 2m53s kube-proxy-nwd7g 1/1 Running 0 2m56s kube-proxy-qpz8t 1/1 Running 0 71m kube-scheduler-master 1/1 Running 0 70m //测试 pod 资源创建 kubectl create deployment nginx --image=nginx kubectl get pods -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES nginx-554b9c67f9-zr2xs 1/1 Running 0 14m 10.244.1.2 node01 //暴露端口提供服务 kubectl expose deployment nginx --port=80 --type=NodePort kubectl get svc NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE kubernetes ClusterIP 10.96.0.1 443/TCP 25h nginx NodePort 10.96.15.132 80:32698/TCP 4s //测试访问 curl http://node01:32698 //扩展3个副本 kubectl scale deployment nginx --replicas=3 kubectl get pods -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES nginx-554b9c67f9-9kh4s 1/1 Running 0 66s 10.244.1.3 node01 nginx-554b9c67f9-rv77q 1/1 Running 0 66s 10.244.2.2 node02 nginx-554b9c67f9-zr2xs 1/1 Running 0 17m 10.244.1.2 node01

------------------------------ 部署 Dashboard ------------------------------ //在 master01 节点上操作 #上传 recommended.yaml 文件到 /opt/k8s 目录中 cd /opt/k8s vim recommended.yaml #默认Dashboard只能集群内部访问,修改Service为NodePort类型,暴露到外部: kind: Service apiVersion: v1 metadata: labels: k8s-app: kubernetes-dashboard name: kubernetes-dashboard namespace: kubernetes-dashboard spec: ports: - port: 443 targetPort: 8443 nodePort: 30001 #添加 type: NodePort #添加 selector: k8s-app: kubernetes-dashboard kubectl apply -f recommended.yaml #创建service account并绑定默认cluster-admin管理员集群角色 kubectl create serviceaccount dashboard-admin -n kube-system kubectl create clusterrolebinding dashboard-admin --clusterrole=cluster-admin --serviceaccount=kube-system:dashboard-admin kubectl describe secrets -n kube-system $(kubectl -n kube-system get secret | awk '/dashboard-admin/{print $1}') #使用输出的token登录Dashboard 安装Harbor私有仓库 --------------------

//修改主机名 hostnamectl set-hostname hub.jingjing.com //所有节点加上主机名映射 echo '192.168.80.13 hub.kgc.com' >> /etc/hosts //安装 docker yum install -y yum-utils device-mapper-persistent-data lvm2 yum-config-manager --add-repo yum install -y docker-ce docker-ce-cli containerd.io mkdir /etc/docker cat > /etc/docker/daemon.json < /etc/docker/daemon.json < 443/TCP 10m service/nginx-deployment ClusterIP 10.96.222.161 30000/TCP 3m15s NAME READY STATUS RESTARTS AGE pod/nginx-deployment-77bcbfbfdc-bv5bz 1/1 Running 0 16s pod/nginx-deployment-77bcbfbfdc-fq8wr 1/1 Running 0 16s pod/nginx-deployment-77bcbfbfdc-xrg45 1/1 Running 0 3m39s yum install ipvsadm -y ipvsadm -Ln curl 10.96.222.161:30000 kubectl edit svc nginx-deployment 25 type: NodePort #把调度策略改成NodePort kubectl get svc NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/kubernetes ClusterIP 10.96.0.1 443/TCP 29m service/nginx-deployment NodePort 10.96.222.161 30000:32340/TCP 22m 浏览器访问: 192.168.19.10:32340 192.168.19.11:32340 192.168.19.17:32340

这个设置 在node1和node2也要设置

版权声明:本文内容由网络用户投稿,版权归原作者所有,本站不拥有其著作权,亦不承担相应法律责任。如果您发现本站中有涉嫌抄袭或描述失实的内容,请联系我们jiasou666@gmail.com 处理,核实后本网站将在24小时内删除侵权内容。

上一篇:k8s readinessProbe+preStop使应用更新时用户无感知
下一篇:k8s helm实战
相关文章

 发表评论

暂时没有评论,来抢沙发吧~