入门K8s：一键脚本搭建Linux服务器集群
好久没有写系列博客了，本文主要是对网上文章的总结篇，主要是将安装和运行代码做了一次真机实验，亲测可用。文章内包含的脚本和代码，多来自于网络，也有我自己的调整和配置，文章末尾对参考的文献做了列举，方便大家参考。
过程很简单，一路next往下看和操作即可，文章不对脚本和代码做原理解释，某些注意点加了红色标注，部分脚本有注释，可以自行参考，以后有机会可以视频讲解。
因为是next的方式，所以本章节主要是操作步骤，步骤中涉及到的代码或者脚本，可以在下文中找到，比如：附录代码一、附录代码二等等，因为脚本实在太长，不太方便放到步骤里。
1、配置 node01 主节点（2个文件）
在root目录下拷贝k8s脚本（附录代码一：kubernetes_node01.sh）和flannel网络（附录代码二：kube-flannel.yml）的文件；
然后给脚本文件赋权限：chmod +x kubernetes_node01.sh
最后执行脚本：./kubernetes_node01.sh
ps：1、sh脚本中，需要配置节点，是内网的。
2、多个节点之间要保证能ping通；
3、中间可能需要自己来配合做些操作，比如输入：y，来做确认等等。
最后，可以在当前文件夹下，看到一个key.txt的文件，里边有安装的结果数据或者密钥等，可查看附录代码三：key.txt，这是我安装的结果，里边有join主节点的配置语句。
查看所有的nodes和pods：
[root@node01 ~]# kubectl get nodesNAME STATUS ROLES AGE VERSIONnode01 Ready master 26h v1.18.0
所有的pods：
[root@node01 ~]# kubectl get pods -ANAMESPACE NAME READY STATUS RESTARTS AGEkube-system coredns-7ff77c879f-6m6fl 1/1 Running 0 25mkube-system coredns-7ff77c879f-dkd56 1/1 Running 0 25mkube-system etcd-node01 1/1 Running 0 26mkube-system kube-apiserver-node01 1/1 Running 0 26mkube-system kube-controller-manager-node01 1/1 Running 0 26mkube-system kube-flannel-ds-amd64-sdv2h 1/1 Running 0 25mkube-system kube-proxy-vgf4r 1/1 Running 0 25mkube-system kube-scheduler-node01 1/1 Running 0 26m
如果都启动，都READY了，表示安装成功。
2、配置dashboard仪表盘（2个文件）
上面安装好了kubectl、kubeadm、kubelet后，我们可以通过客户端来连接，这里安利下k8s的客户端：Lens，很香。
如果不用客户端，那就需要安装仪表盘了。
1、Linux根目录拷贝文件，附录代码四：recommended.yaml（安装看板），附录代码五：dashboard-svc-account.yaml（配置管理员账户）
2、执行命令：
sed -i '/targetPort: 8443/a\ \ \ \ \ \ nodePort: 30001\n\ \ type: NodePort' recommended.yaml3、启动仪表盘服务：
kubectl apply -f recommended.yaml4、启动配置账户：
kubectl apply -f dashboard-svc-account.yaml
都成功后，会生成一个token字符串，用来登录web端的令牌的，如果没有拷贝或者丢失了也不怕，可以使用命令查看：
kubectl describe secrets -n kube-system `kubectl get secret -n kube-system | grep admin | awk '{print $1}'` | grep '^token'|awk '{print $2}'token就是类似这种：
eyJhbGciOiJSUzI1NiIsImtpZCI6Ikl5SE00cXFZR1V2cWstQURVcGlUOGk4cTBYekZMV0VmNDEwRy14UTd1d2sifQ.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJrdWJlLXN5c3RlbSIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VjcmV0Lm5hbWUiOiJkYXNoYm9hcmQtYWRtaW4tdG9rZW4tY3JnejYiLCJrdWJlcm5ldGVzLmlvL3NlcnZpY2VhY2NvdW50L3NlcnZpY2UtYWNjb3VudC5uYW1lIjoiZGFzaGJvYXJkLWFkbWliwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9zZXJ2aWNlLWFjY291bnQudWlkIjoiMjYwMGQ0ZjctM2ZhOS00ODIwLWFmMmUtZTJlZDMxYWMyYWFhIiwic3ViIjoic3lzdGVtOnNlcnZpY2VhY2NvdW50Omt1YmUtc3lzdGVtOmRhc2hib2FyZC1hZG1pbiJ9.BBtdG-S2kHEwRbWIAf6DiUgC3ILUOStPATyWfvxcQs5VJBtLRyMGqQ-AfkUoVLuhZdUv-CGoEJ1OYA00M6MwoehDdkhLFbXF7Xx1IPyhFTHxZ_oXHBPyjEREkTEerarZnvgt0ufU4g_Eqn91jdHet73itz-0abgmLMPkRl5YYjlh36Ivwq9IjKgujLwTNisUFckLuHOscHtQIrjIvAZlWTRh_awMsDHvemAKG_YIjMbyQnXi6VfN3rTW869DA0XAGOF2t7cWBtMmHvmLxVYqpOauUzwXXeYbO9eP0_d9JtVwKv6R0Q7sexRFZ-iTdZBOJDujFI3UT2jsqgVdbagA
这里再检查下：
查看所有的nodes和pods：
[root@node01 ~]# kubectl get pods -ANAMESPACE NAME READY STATUS RESTARTS AGEkube-system coredns-7ff77c879f-6m6fl 1/1 Running 0 25mkube-system coredns-7ff77c879f-dkd56 1/1 Running 0 25mkube-system etcd-node01 1/1 Running 0 26mkube-system kube-apiserver-node01 1/1 Running 0 26mkube-system kube-controller-manager-node01 1/1 Running 0 26mkube-system kube-flannel-ds-amd64-sdv2h 1/1 Running 0 25mkube-system kube-proxy-vgf4r 1/1 Running 0 25mkube-system kube-scheduler-node01 1/1 Running 0 26mkubernetes-dashboard dashboard-metrics-scraper-78f5d9f487-ldswx 1/1 Running 0 12mkubernetes-dashboard kubernetes-dashboard-577bd97bc-szvwt 1/1 Running 0 12m
多了kubernetes-dashboard命名空间下的两个pod。
3、配置 node02 子节点（1个文件）
如果你没有多余的服务器，也可以在master节点做自己的pod的，需要开启下，命令将 master 标记为可调度：
sudo kubectl taint nodes --all node-role.kubernetes.io/masteflr-
如果要配置多个子节点，那就仿照主节点来继续写sh脚本吧（附录代码六：kubernetes_node02.sh），步骤和主节点一致：
1、拷贝到子节点服务器；
2、赋权限，执行文件：./kubernetes_node02.sh
3、这里不用flannel配置；
4、安装完成后，可以join到主节点，配置文件在主节点的key.txt文件里，如果你安装成功了的话；
kubeadm join 172.17.10.4:6443 --token q3uu1o.4rdfkcyzxjhawvk1 \--discovery-token-ca-cert-hash sha256:a755d8f56733ba8f9d1951298b200202fce7b84389954bf7a38558fa6ce2a9c9
如果一切正常，可以去主节点查看所有的nodes：
NAME STATUS ROLES AGE VERSIONnode01 Ready master 26h v1.18.0node02 Ready <none> 25h v1.18.0
表示我们的子节点已经配置完成。
4、配置ASP.Net Core服务
这里的Deployment+Service的写法比较简单，直接贴出来，就不做过多的解释了。
apiVersion: apps/v1kind: Deploymentmetadata:labels:app: laozhang-op2name: laozhang-op2spec:selector:matchLabels:app: laozhang-op2replicas: 2template:metadata:labels:app: laozhang-op2spec:containers:name: laozhang-op2image: laozhangisphi/apkimg315imagePullPolicy: IfNotPresent #pull镜像时机，----apiVersion: v1kind: Servicemetadata:name: laozhang-op2spec:type: NodePortports:name: defaultprotocol: TCPport: 80targetPort: 80nodePort: 30099selector:app: laozhang-op2
但是这种是nodePort的方式，平时使用更多的是Ingress的方式，那使用ingress，就先需要配置ingress的服务。
5、配置Ingress-nginx（1个文件）
在根目录拷贝文件，附录代码七：mandatory.yaml，配置Ingress-Nginx服务，
这里需要注意下，如果服务器之前已经配置过nginx，需要在mandatory.yaml文件中，修改http-port输出端口，详细内容见下面的代码，有注释。
直接执行yaml：
kubectl apply -f mandatory.yaml
如果没有报错，可以查看所有的pods：
[root@node01 ~]# kubectl get pods -ANAMESPACE NAME READY STATUS RESTARTS AGEdefault laozhang-op2-5cf487b57f-pdvfg 1/1 Running 0 4h29mdefault laozhang-op2-5cf487b57f-vtgwc 1/1 Running 0 4h29mingress-nginx nginx-ingress-controller-557475687f-rfl98 1/1 Running 0 122mkube-system coredns-7ff77c879f-gj4sl 1/1 Running 0 26hkube-system coredns-7ff77c879f-mqp2q 1/1 Running 0 26hkube-system etcd-node01 1/1 Running 0 26hkube-system kube-apiserver-node01 1/1 Running 0 26hkube-system kube-controller-manager-node01 1/1 Running 0 26hkube-system kube-flannel-ds-amd64-nmnj2 1/1 Running 0 26hkube-system kube-proxy-wcjb8 1/1 Running 0 26hkube-system kube-scheduler-node01 1/1 Running 2 26hkubernetes-dashboard dashboard-metrics-scraper-78f5d9f487-qp2fw 1/1 Running 0 26hkubernetes-dashboard kubernetes-dashboard-577bd97bc-2tsj7 1/1 Running 0 26h
如果和上面一样，那恭喜，一切配置就完成了。
附录代码一：kubernetes_node01.sh
#!/bin/bash################主节点#################### 第一部分，环境初始化 #####k8s版本version=v1.18.0kubelet=kubelet-1.18.0-0.x86_64kubeadm=kubeadm-1.18.0-0.x86_64kubectl=kubectl-1.18.0-0.x86_64#集群加入方式key=/root/key.txt#部署flannel网络flannel=/root/kube-flannel.yml#安装必要依赖yum -y install vim wget git cmake make gcc gcc-c++ net-tools lrzsz#### 第二部分，节点配置 #####主机解析，免密登录#内网ip，配置多节点，也可以不配置，后期通过join的方式node01=172.21.10.4#node02=192.168.10.7#node03=192.168.1.30hostnamectl set-hostname node01echo '172.21.10.4 node01#192.168.10.7 node02#192.168.1.30 node03' >> /etc/hostsssh-keygen-i $node01#ssh-copy-id -i $node02#ssh-copy-id -i $node03#scp /etc/hosts node02:/etc/hosts#scp /etc/hosts node03:/etc/hosts#关闭防火墙systemctl stop firewalldsystemctl disable firewalld#swap分区关闭swapoff -ased -i 's/.*swap.*/#&/' /etc/fstab#关闭沙盒setenforce 0sed -i "s/^SELINUX=enforcing/SELINUX=disabled/g" /etc/sysconfig/selinuxsed -i "s/^SELINUX=enforcing/SELINUX=disabled/g" /etc/selinux/configsed -i "s/^SELINUX=permissive/SELINUX=disabled/g" /etc/sysconfig/selinuxsed -i "s/^SELINUX=permissive/SELINUX=disabled/g" /etc/selinux/config#打开ipv6modprobe br_netfiltermodprobe ip_vs_rrcat <<EOF > /etc/sysctl.d/k8s.conf= 1= 1= 0EOFsysctl -p /etc/sysctl.d/k8s.confls /proc/sys/net/bridge#### 第三部分，参数/源处理 #####安装epel源yum install -y epel-releaseyum install -y yum-utils device-mapper-persistent-data lvm2 net-tools conntrack-tools wget vim ntpdate libseccomp libtool-ltdl#时区校准systemctl enable ntpdate.serviceecho '*/30 * * * * /usr/sbin/ntpdate time7.aliyun.com >/dev/null 2>&1' > /tmp/crontab2.tmpcrontab /tmp/crontab2.tmpsystemctl start ntpdate.service#添加参数echo "* soft nofile 65536" >> /etc/security/limits.confecho "* hard nofile 65536" >> /etc/security/limits.confecho "* soft nproc 65536" >> /etc/security/limits.confecho "* hard nproc 65536" >> /etc/security/limits.confecho "* soft memlock unlimited" >> /etc/security/limits.confecho "* hard memlock unlimited" >> /etc/security/limits.conf#添加kubernetes的epel源echo '[kubernetes]name=Kubernetesbaseurl=https://mirrors.aliyun.com/kubernetes/yum/repos/kubernetes-el7-x86_64/enabled=1gpgcheck=1repo_gpgcheck=1gpgkey=https://mirrors.aliyun.com/kubernetes/yum/doc/yum-key.gpg https://mirrors.aliyun.com/kubernetes/yum/doc/rpm-package-key.gpg' > /etc/yum.repos.d/kubernetes.repo#下载sudo yum-config-manager \--add-repo \https://mirrors.ustc.edu.cn/docker-ce/linux/centos/docker-ce.repoyum makecache fast#### 第四部分，开始安装 ####yum -y install docker-ceyum install --enablerepo="kubernetes" $kubelet $kubeadm $kubectlsystemctl enable kubelet.service && systemctl start kubelet.servicesystemctl start docker.service && systemctl enable docker.service#安装tab快捷键yum -y install bash-completion && source /usr/share/bash-completion/bash_completion && source <(kubectl completion bash) && echo "source <(kubectl completion bash)" >> ~/.bashrc#创建集群kubeadm init --apiserver-advertise-address $node01 --image-repository registry.aliyuncs.com/google_containers --kubernetes-version $version --pod-network-cidr=10.244.0.0/16 >> $key 2>&1export KUBECONFIG=/etc/kubernetes/admin.confmkdir -p $HOME/.kubesudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/configsudo chown $(id -u):$(id -g) $HOME/.kube/configdocker pull quay.io/coreos/flannel:v0.12.0-amd64kubectl apply -f $flannelecho '请手动查看$key文件的密钥将其他节点接入集群'
附录代码二：kube-flannel.yml
################flannel网络################---apiVersion: policy/v1beta1kind: PodSecurityPolicymetadata:name: psp.flannel.unprivilegedannotations:: docker/default: docker/default: runtime/default: runtime/defaultspec:privileged: falsevolumes:configMapsecretemptyDirhostPathallowedHostPaths:pathPrefix: "/etc/cni/net.d"pathPrefix: "/etc/kube-flannel"pathPrefix: "/run/flannel"readOnlyRootFilesystem: false# Users and groupsrunAsUser:rule: RunAsAnysupplementalGroups:rule: RunAsAnyfsGroup:rule: RunAsAny# Privilege EscalationallowPrivilegeEscalation: falsedefaultAllowPrivilegeEscalation: false# CapabilitiesallowedCapabilities: ['NET_ADMIN']defaultAddCapabilities: []requiredDropCapabilities: []# Host namespaceshostPID: falsehostIPC: falsehostNetwork: truehostPorts:min: 0max: 65535# SELinuxseLinux:# SELinux is unused in CaaSPrule: 'RunAsAny'---kind: ClusterRoleapiVersion: rbac.authorization.k8s.io/v1beta1metadata:name: flannelrules:apiGroups: ['extensions']resources: ['podsecuritypolicies']verbs: ['use']resourceNames: ['psp.flannel.unprivileged']apiGroups:""resources:podsverbs:getapiGroups:""resources:nodesverbs:listwatchapiGroups:""resources:nodes/statusverbs:patch---kind: ClusterRoleBindingapiVersion: rbac.authorization.k8s.io/v1beta1metadata:name: flannelroleRef:apiGroup: rbac.authorization.k8s.iokind: ClusterRolename: flannelsubjects:kind: ServiceAccountname: flannelnamespace: kube-system---apiVersion: v1kind: ServiceAccountmetadata:name: flannelnamespace: kube-system---kind: ConfigMapapiVersion: v1metadata:name: kube-flannel-cfgnamespace: kube-systemlabels:tier: nodeapp: flanneldata:: |{: "cbr0",: "0.3.1",: [{: "flannel",: {: true,: true}},{: "portmap",: {: true}}]}: |{: "10.244.0.0/16",: {: "vxlan"}}---apiVersion: apps/v1kind: DaemonSetmetadata:name: kube-flannel-ds-amd64namespace: kube-systemlabels:tier: nodeapp: flannelspec:selector:matchLabels:app: flanneltemplate:metadata:labels:tier: nodeapp: flannelspec:affinity:nodeAffinity:requiredDuringSchedulingIgnoredDuringExecution:nodeSelectorTerms:matchExpressions:key: kubernetes.io/osoperator: Invalues:linuxkey: kubernetes.io/archoperator: Invalues:amd64hostNetwork: truetolerations:operator: Existseffect: NoScheduleserviceAccountName: flannelinitContainers:name: install-cniimage: quay.io/coreos/flannel:v0.12.0-amd64command:cpargs:-f/etc/kube-flannel/cni-conf.json/etc/cni/net.d/10-flannel.conflistvolumeMounts:name: cnimountPath: /etc/cni/net.dname: flannel-cfgmountPath: /etc/kube-flannel/containers:name: kube-flannelimage: quay.io/coreos/flannel:v0.12.0-amd64command:/opt/bin/flanneldargs:--ip-masq--kube-subnet-mgrresources:requests:cpu: "100m"memory: "50Mi"limits:cpu: "100m"memory: "50Mi"securityContext:privileged: falsecapabilities:add: ["NET_ADMIN"]env:name: POD_NAMEvalueFrom:fieldRef:fieldPath: metadata.namename: POD_NAMESPACEvalueFrom:fieldRef:fieldPath: metadata.namespacevolumeMounts:name: runmountPath: /run/flannelname: flannel-cfgmountPath: /etc/kube-flannel/volumes:name: runhostPath:path: /run/flannelname: cnihostPath:path: /etc/cni/net.dname: flannel-cfgconfigMap:name: kube-flannel-cfg---apiVersion: apps/v1kind: DaemonSetmetadata:name: kube-flannel-ds-arm64namespace: kube-systemlabels:tier: nodeapp: flannelspec:selector:matchLabels:app: flanneltemplate:metadata:labels:tier: nodeapp: flannelspec:affinity:nodeAffinity:requiredDuringSchedulingIgnoredDuringExecution:nodeSelectorTerms:matchExpressions:key: kubernetes.io/osoperator: Invalues:linuxkey: kubernetes.io/archoperator: Invalues:arm64hostNetwork: truetolerations:operator: Existseffect: NoScheduleserviceAccountName: flannelinitContainers:name: install-cniimage: quay.io/coreos/flannel:v0.12.0-arm64command:cpargs:-f/etc/kube-flannel/cni-conf.json/etc/cni/net.d/10-flannel.conflistvolumeMounts:name: cnimountPath: /etc/cni/net.dname: flannel-cfgmountPath: /etc/kube-flannel/containers:name: kube-flannelimage: quay.io/coreos/flannel:v0.12.0-arm64command:/opt/bin/flanneldargs:--ip-masq--kube-subnet-mgrresources:requests:cpu: "100m"memory: "50Mi"limits:cpu: "100m"memory: "50Mi"securityContext:privileged: falsecapabilities:add: ["NET_ADMIN"]env:name: POD_NAMEvalueFrom:fieldRef:fieldPath: metadata.namename: POD_NAMESPACEvalueFrom:fieldRef:fieldPath: metadata.namespacevolumeMounts:name: runmountPath: /run/flannelname: flannel-cfgmountPath: /etc/kube-flannel/volumes:name: runhostPath:path: /run/flannelname: cnihostPath:path: /etc/cni/net.dname: flannel-cfgconfigMap:name: kube-flannel-cfg---apiVersion: apps/v1kind: DaemonSetmetadata:name: kube-flannel-ds-armnamespace: kube-systemlabels:tier: nodeapp: flannelspec:selector:matchLabels:app: flanneltemplate:metadata:labels:tier: nodeapp: flannelspec:affinity:nodeAffinity:requiredDuringSchedulingIgnoredDuringExecution:nodeSelectorTerms:matchExpressions:key: kubernetes.io/osoperator: Invalues:linuxkey: kubernetes.io/archoperator: Invalues:armhostNetwork: truetolerations:operator: Existseffect: NoScheduleserviceAccountName: flannelinitContainers:name: install-cniimage: quay.io/coreos/flannel:v0.12.0-armcommand:cpargs:-f/etc/kube-flannel/cni-conf.json/etc/cni/net.d/10-flannel.conflistvolumeMounts:name: cnimountPath: /etc/cni/net.dname: flannel-cfgmountPath: /etc/kube-flannel/containers:name: kube-flannelimage: quay.io/coreos/flannel:v0.12.0-armcommand:/opt/bin/flanneldargs:--ip-masq--kube-subnet-mgrresources:requests:cpu: "100m"memory: "50Mi"limits:cpu: "100m"memory: "50Mi"securityContext:privileged: falsecapabilities:add: ["NET_ADMIN"]env:name: POD_NAMEvalueFrom:fieldRef:fieldPath: metadata.namename: POD_NAMESPACEvalueFrom:fieldRef:fieldPath: metadata.namespacevolumeMounts:name: runmountPath: /run/flannelname: flannel-cfgmountPath: /etc/kube-flannel/volumes:name: runhostPath:path: /run/flannelname: cnihostPath:path: /etc/cni/net.dname: flannel-cfgconfigMap:name: kube-flannel-cfg---apiVersion: apps/v1kind: DaemonSetmetadata:name: kube-flannel-ds-ppc64lenamespace: kube-systemlabels:tier: nodeapp: flannelspec:selector:matchLabels:app: flanneltemplate:metadata:labels:tier: nodeapp: flannelspec:affinity:nodeAffinity:requiredDuringSchedulingIgnoredDuringExecution:nodeSelectorTerms:matchExpressions:key: kubernetes.io/osoperator: Invalues:linuxkey: kubernetes.io/archoperator: Invalues:ppc64lehostNetwork: truetolerations:operator: Existseffect: NoScheduleserviceAccountName: flannelinitContainers:name: install-cniimage: quay.io/coreos/flannel:v0.12.0-ppc64lecommand:cpargs:-f/etc/kube-flannel/cni-conf.json/etc/cni/net.d/10-flannel.conflistvolumeMounts:name: cnimountPath: /etc/cni/net.dname: flannel-cfgmountPath: /etc/kube-flannel/containers:name: kube-flannelimage: quay.io/coreos/flannel:v0.12.0-ppc64lecommand:/opt/bin/flanneldargs:--ip-masq--kube-subnet-mgrresources:requests:cpu: "100m"memory: "50Mi"limits:cpu: "100m"memory: "50Mi"securityContext:privileged: falsecapabilities:add: ["NET_ADMIN"]env:name: POD_NAMEvalueFrom:fieldRef:fieldPath: metadata.namename: POD_NAMESPACEvalueFrom:fieldRef:fieldPath: metadata.namespacevolumeMounts:name: runmountPath: /run/flannelname: flannel-cfgmountPath: /etc/kube-flannel/volumes:name: runhostPath:path: /run/flannelname: cnihostPath:path: /etc/cni/net.dname: flannel-cfgconfigMap:name: kube-flannel-cfg---apiVersion: apps/v1kind: DaemonSetmetadata:name: kube-flannel-ds-s390xnamespace: kube-systemlabels:tier: nodeapp: flannelspec:selector:matchLabels:app: flanneltemplate:metadata:labels:tier: nodeapp: flannelspec:affinity:nodeAffinity:requiredDuringSchedulingIgnoredDuringExecution:nodeSelectorTerms:matchExpressions:key: kubernetes.io/osoperator: Invalues:linuxkey: kubernetes.io/archoperator: Invalues:s390xhostNetwork: truetolerations:operator: Existseffect: NoScheduleserviceAccountName: flannelinitContainers:name: install-cniimage: quay.io/coreos/flannel:v0.12.0-s390xcommand:cpargs:-f/etc/kube-flannel/cni-conf.json/etc/cni/net.d/10-flannel.conflistvolumeMounts:name: cnimountPath: /etc/cni/net.dname: flannel-cfgmountPath: /etc/kube-flannel/containers:name: kube-flannelimage: quay.io/coreos/flannel:v0.12.0-s390xcommand:/opt/bin/flanneldargs:--ip-masq--kube-subnet-mgrresources:requests:cpu: "100m"memory: "50Mi"limits:cpu: "100m"memory: "50Mi"securityContext:privileged: falsecapabilities:add: ["NET_ADMIN"]env:name: POD_NAMEvalueFrom:fieldRef:fieldPath: metadata.namename: POD_NAMESPACEvalueFrom:fieldRef:fieldPath: metadata.namespacevolumeMounts:name: runmountPath: /run/flannelname: flannel-cfgmountPath: /etc/kube-flannel/volumes:name: runhostPath:path: /run/flannelname: cnihostPath:path: /etc/cni/net.dname: flannel-cfgconfigMap:name: kube-flannel-cfg
附录代码三：key.txt
W0526 16:17:20.680490 13760 configset.go:202] WARNING: kubeadm cannot validate component configs for API groups [kubelet.config.k8s.io kubeproxy.config.k8s.io][init] Using Kubernetes version: v1.18.0[preflight] Running pre-flight checks[WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at https://kubernetes.io/docs/setup/cri/[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'[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"[kubelet-start] Starting the kubelet[certs] Using certificateDir folder "/etc/kubernetes/pki"[certs] Generating "ca" certificate and key[certs] Generating "apiserver" certificate and key[certs] apiserver serving cert is signed for DNS names [node01 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 172.17.10.4][certs] Generating "apiserver-kubelet-client" certificate and key[certs] Generating "front-proxy-ca" certificate and key[certs] Generating "front-proxy-client" certificate and key[certs] Generating "etcd/ca" certificate and key[certs] Generating "etcd/server" certificate and key[certs] etcd/server serving cert is signed for DNS names [node01 localhost] and IPs [172.17.10.4 127.0.0.1 ::1][certs] Generating "etcd/peer" certificate and key[certs] etcd/peer serving cert is signed for DNS names [node01 localhost] and IPs [172.17.10.4 127.0.0.1 ::1][certs] Generating "etcd/healthcheck-client" certificate and key[certs] Generating "apiserver-etcd-client" certificate and key[certs] Generating "sa" key and public key[kubeconfig] Using kubeconfig folder "/etc/kubernetes"[kubeconfig] Writing "admin.conf" kubeconfig file[kubeconfig] Writing "kubelet.conf" kubeconfig file[kubeconfig] Writing "controller-manager.conf" kubeconfig file[kubeconfig] Writing "scheduler.conf" kubeconfig file[control-plane] Using manifest folder "/etc/kubernetes/manifests"[control-plane] Creating static Pod manifest for "kube-apiserver"[control-plane] Creating static Pod manifest for "kube-controller-manager"W0526 16:18:02.560249 13760 manifests.go:225] the default kube-apiserver authorization-mode is "Node,RBAC"; using "Node,RBAC"[control-plane] Creating static Pod manifest for "kube-scheduler"W0526 16:18:02.561130 13760 manifests.go:225] the default kube-apiserver authorization-mode is "Node,RBAC"; using "Node,RBAC"[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s[apiclient] All control plane components are healthy after 26.504466 seconds[upload-config] Storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace[kubelet] Creating a ConfigMap "kubelet-config-1.18" in namespace kube-system with the configuration for the kubelets in the cluster[upload-certs] Skipping phase. Please see --upload-certs[mark-control-plane] Marking the node node01 as control-plane by adding the label "node-role.kubernetes.io/master=''"[mark-control-plane] Marking the node node01 as control-plane by adding the taints [node-role.kubernetes.io/master:NoSchedule][bootstrap-token] Using token: q3uu1o.4rdfkcyzxjhawvk1[bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles[bootstrap-token] configured RBAC rules to allow Node Bootstrap tokens to get nodes[bootstrap-token] configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials[bootstrap-token] configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token[bootstrap-token] configured RBAC rules to allow certificate rotation for all node client certificates in the cluster[bootstrap-token] Creating the "cluster-info" ConfigMap in the "kube-public" namespace[kubelet-finalize] Updating "/etc/kubernetes/kubelet.conf" to point to a rotatable kubelet client certificate and key[addons] Applied essential addon: CoreDNS[addons] Applied essential addon: kube-proxyYour Kubernetes control-plane has initialized successfully!To start using your cluster, you need to run the following as a regular user:mkdir -p $HOME/.kubesudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/configsudo chown $(id -u):$(id -g) $HOME/.kube/configYou 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 172.17.10.4:6443 --token q3uu1o.4rdfkcyzxjhawvk1 \--discovery-token-ca-cert-hash sha256:a755d8f56733ba8f9d1951298b200202fce7b84389954bf7a38558fa6ce2a9c9
附录代码四：recommended.yaml
# Copyright 2017 The Kubernetes Authors.## Licensed under the Apache License, Version 2.0 (the "License");# you may not use this file except in compliance with the License.# You may obtain a copy of the License at## http://www.apache.org/licenses/LICENSE-2.0## Unless required by applicable law or agreed to in writing, software# distributed under the License is distributed on an "AS IS" BASIS,# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.# See the License for the specific language governing permissions and# limitations under the License.################安装dashboard################apiVersion: v1kind: Namespacemetadata:name: kubernetes-dashboard---apiVersion: v1kind: ServiceAccountmetadata:labels:: kubernetes-dashboardname: kubernetes-dashboardnamespace: kubernetes-dashboard---kind: ServiceapiVersion: v1metadata:labels:: kubernetes-dashboardname: kubernetes-dashboardnamespace: kubernetes-dashboardspec:ports:port: 443targetPort: 8443selector:: kubernetes-dashboard---apiVersion: v1kind: Secretmetadata:labels:: kubernetes-dashboardname: kubernetes-dashboard-certsnamespace: kubernetes-dashboardtype: Opaque---apiVersion: v1kind: Secretmetadata:labels:: kubernetes-dashboardname: kubernetes-dashboard-csrfnamespace: kubernetes-dashboardtype: Opaquedata:csrf: ""---apiVersion: v1kind: Secretmetadata:labels:: kubernetes-dashboardname: kubernetes-dashboard-key-holdernamespace: kubernetes-dashboardtype: Opaque---kind: ConfigMapapiVersion: v1metadata:labels:: kubernetes-dashboardname: kubernetes-dashboard-settingsnamespace: kubernetes-dashboard---kind: RoleapiVersion: rbac.authorization.k8s.io/v1metadata:labels:: kubernetes-dashboardname: kubernetes-dashboardnamespace: kubernetes-dashboardrules:# Allow Dashboard to get, update and delete Dashboard exclusive secrets.apiGroups: [""]resources: ["secrets"]resourceNames: ["kubernetes-dashboard-key-holder", "kubernetes-dashboard-certs", "kubernetes-dashboard-csrf"]verbs: ["get", "update", "delete"]# Allow Dashboard to get and update 'kubernetes-dashboard-settings' config map.apiGroups: [""]resources: ["configmaps"]resourceNames: ["kubernetes-dashboard-settings"]verbs: ["get", "update"]# Allow Dashboard to get metrics.apiGroups: [""]resources: ["services"]resourceNames: ["heapster", "dashboard-metrics-scraper"]verbs: ["proxy"]apiGroups: [""]resources: ["services/proxy"]resourceNames: ["heapster", "http:heapster:", "https:heapster:", "dashboard-metrics-scraper", "http:dashboard-metrics-scraper"]verbs: ["get"]---kind: ClusterRoleapiVersion: rbac.authorization.k8s.io/v1metadata:labels:: kubernetes-dashboardname: kubernetes-dashboardrules:# Allow Metrics Scraper to get metrics from the Metrics serverapiGroups: ["metrics.k8s.io"]resources: ["pods", "nodes"]verbs: ["get", "list", "watch"]---apiVersion: rbac.authorization.k8s.io/v1kind: RoleBindingmetadata:labels:: kubernetes-dashboardname: kubernetes-dashboardnamespace: kubernetes-dashboardroleRef:apiGroup: rbac.authorization.k8s.iokind: Rolename: kubernetes-dashboardsubjects:kind: ServiceAccountname: kubernetes-dashboardnamespace: kubernetes-dashboard---apiVersion: rbac.authorization.k8s.io/v1kind: ClusterRoleBindingmetadata:name: kubernetes-dashboardroleRef:apiGroup: rbac.authorization.k8s.iokind: ClusterRolename: kubernetes-dashboardsubjects:kind: ServiceAccountname: kubernetes-dashboardnamespace: kubernetes-dashboard---kind: DeploymentapiVersion: apps/v1metadata:labels:: kubernetes-dashboardname: kubernetes-dashboardnamespace: kubernetes-dashboardspec:replicas: 1revisionHistoryLimit: 10selector:matchLabels:: kubernetes-dashboardtemplate:metadata:labels:: kubernetes-dashboardspec:containers:name: kubernetes-dashboardimage: kubernetesui/dashboard:v2.2.0imagePullPolicy: Alwaysports:containerPort: 8443protocol: TCPargs:--auto-generate-certificates--namespace=kubernetes-dashboard# Uncomment the following line to manually specify Kubernetes API server Host# If not specified, Dashboard will attempt to auto discover the API server and connect# to it. Uncomment only if the default does not work.# - --apiserver-host=http://my-address:portvolumeMounts:name: kubernetes-dashboard-certsmountPath: /certs# Create on-disk volume to store exec logsmountPath: /tmpname: tmp-volumelivenessProbe:httpGet:scheme: HTTPSpath: /port: 8443initialDelaySeconds: 30timeoutSeconds: 30securityContext:allowPrivilegeEscalation: falsereadOnlyRootFilesystem: truerunAsUser: 1001runAsGroup: 2001volumes:name: kubernetes-dashboard-certssecret:secretName: kubernetes-dashboard-certsname: tmp-volumeemptyDir: {}serviceAccountName: kubernetes-dashboardnodeSelector:: linux# Comment the following tolerations if Dashboard must not be deployed on mastertolerations:key: node-role.kubernetes.io/mastereffect: NoSchedule---kind: ServiceapiVersion: v1metadata:labels:: dashboard-metrics-scrapername: dashboard-metrics-scrapernamespace: kubernetes-dashboardspec:ports:port: 8000targetPort: 8000selector:: dashboard-metrics-scraper---kind: DeploymentapiVersion: apps/v1metadata:labels:: dashboard-metrics-scrapername: dashboard-metrics-scrapernamespace: kubernetes-dashboardspec:replicas: 1revisionHistoryLimit: 10selector:matchLabels:: dashboard-metrics-scrapertemplate:metadata:labels:: dashboard-metrics-scraperannotations:: 'runtime/default'spec:containers:name: dashboard-metrics-scraperimage: kubernetesui/metrics-scraper:v1.0.6ports:containerPort: 8000protocol: TCPlivenessProbe:httpGet:scheme: HTTPpath: /port: 8000initialDelaySeconds: 30timeoutSeconds: 30volumeMounts:mountPath: /tmpname: tmp-volumesecurityContext:allowPrivilegeEscalation: falsereadOnlyRootFilesystem: truerunAsUser: 1001runAsGroup: 2001serviceAccountName: kubernetes-dashboardnodeSelector:: linux# Comment the following tolerations if Dashboard must not be deployed on mastertolerations:key: node-role.kubernetes.io/mastereffect: NoSchedulevolumes:name: tmp-volumeemptyDir: {}
附录代码五：dashboard-svc-account.yaml
################配置dashboard管理员账号################apiVersion: v1kind: ServiceAccountmetadata:name: dashboard-adminnamespace: kube-system---apiVersion: rbac.authorization.k8s.io/v1kind: ClusterRoleBindingmetadata:name: dashboard-adminroleRef:apiGroup: rbac.authorization.k8s.iokind: ClusterRolename: cluster-adminsubjects:kind: ServiceAccountname: dashboard-adminnamespace: kube-system
附录代码六：kubernetes_node02.sh
#!/bin/bash################子节点#################### 第一部分，环境初始化 #####k8s版本version=v1.18.0kubelet=kubelet-1.18.0-0.x86_64kubeadm=kubeadm-1.18.0-0.x86_64kubectl=kubectl-1.18.0-0.x86_64#集群加入方式key=/root/key.txt#部署flannel网络flannel=/root/kube-flannel.yml#安装必要依赖yum -y install vim wget git cmake make gcc gcc-c++ net-tools lrzsz#### 第二部分，节点配置 #####配置节点，主机解析，免密登录node01=172.17.10.4node02=172.17.10.7# node03=192.168.1.30hostnamectl set-hostname node02echo '172.17.10.4 node01node02' >> /etc/hostsssh-keygen-i $node01-i $node02# ssh-copy-id -i $node03scp /etc/hosts node02:/etc/hosts# scp /etc/hosts node03:/etc/hosts#关闭防火墙systemctl stop firewalldsystemctl disable firewalld#swap分区关闭swapoff -ased -i 's/.*swap.*/#&/' /etc/fstab#关闭沙盒setenforce 0sed -i "s/^SELINUX=enforcing/SELINUX=disabled/g" /etc/sysconfig/selinuxsed -i "s/^SELINUX=enforcing/SELINUX=disabled/g" /etc/selinux/configsed -i "s/^SELINUX=permissive/SELINUX=disabled/g" /etc/sysconfig/selinuxsed -i "s/^SELINUX=permissive/SELINUX=disabled/g" /etc/selinux/config#打开ipv6modprobe br_netfiltermodprobe ip_vs_rrcat <<EOF > /etc/sysctl.d/k8s.conf= 1= 1= 0EOFsysctl -p /etc/sysctl.d/k8s.confls /proc/sys/net/bridge#### 第三部分，参数/源处理 #####安装epel源yum install -y epel-releaseyum install -y yum-utils device-mapper-persistent-data lvm2 net-tools conntrack-tools wget vim ntpdate libseccomp libtool-ltdl#时区校准systemctl enable ntpdate.serviceecho '*/30 * * * * /usr/sbin/ntpdate time7.aliyun.com >/dev/null 2>&1' > /tmp/crontab2.tmpcrontab /tmp/crontab2.tmpsystemctl start ntpdate.service#添加参数echo "* soft nofile 65536" >> /etc/security/limits.confecho "* hard nofile 65536" >> /etc/security/limits.confecho "* soft nproc 65536" >> /etc/security/limits.confecho "* hard nproc 65536" >> /etc/security/limits.confecho "* soft memlock unlimited" >> /etc/security/limits.confecho "* hard memlock unlimited" >> /etc/security/limits.conf#添加kubernetes的epel源echo '[kubernetes]name=Kubernetesbaseurl=https://mirrors.aliyun.com/kubernetes/yum/repos/kubernetes-el7-x86_64/enabled=1gpgcheck=1repo_gpgcheck=1gpgkey=https://mirrors.aliyun.com/kubernetes/yum/doc/yum-key.gpg https://mirrors.aliyun.com/kubernetes/yum/doc/rpm-package-key.gpg' > /etc/yum.repos.d/kubernetes.repo#下载sudo yum-config-manager \--add-repo \https://mirrors.ustc.edu.cn/docker-ce/linux/centos/docker-ce.repoyum makecache fast#### 第四部分，开始安装 ####yum -y install docker-ceyum install --enablerepo="kubernetes" $kubelet $kubeadm $kubectlsystemctl enable kubelet.service && systemctl start kubelet.servicesystemctl start docker.service && systemctl enable docker.service#安装tab快捷键yum -y install bash-completion && source /usr/share/bash-completion/bash_completion && source <(kubectl completion bash) && echo "source <(kubectl completion bash)" >> ~/.bashrc#创建集群docker pull quay.io/coreos/flannel:v0.12.0-amd64echo '请手动查看主节点$key文件的密钥将其他节点接入集群'
附录代码七：mandatory.yaml
################配置ingress-nginx服务################apiVersion: v1kind: Namespacemetadata:name: ingress-nginxlabels:: ingress-nginx: ingress-nginx---kind: ConfigMapapiVersion: v1metadata:name: nginx-configurationnamespace: ingress-nginxlabels:: ingress-nginx: ingress-nginx---kind: ConfigMapapiVersion: v1metadata:name: tcp-servicesnamespace: ingress-nginxlabels:: ingress-nginx: ingress-nginx---kind: ConfigMapapiVersion: v1metadata:name: udp-servicesnamespace: ingress-nginxlabels:: ingress-nginx: ingress-nginx---apiVersion: v1kind: ServiceAccountmetadata:name: nginx-ingress-serviceaccountnamespace: ingress-nginxlabels:: ingress-nginx: ingress-nginx---apiVersion: rbac.authorization.k8s.io/v1beta1kind: ClusterRolemetadata:name: nginx-ingress-clusterrolelabels:: ingress-nginx: ingress-nginxrules:apiGroups:""resources:configmapsendpointsnodespodssecretsverbs:listwatchapiGroups:""resources:nodesverbs:getapiGroups:""resources:servicesverbs:getlistwatchapiGroups:""resources:eventsverbs:createpatchapiGroups:"extensions""networking.k8s.io"resources:ingressesverbs:getlistwatchapiGroups:"extensions""networking.k8s.io"resources:ingresses/statusverbs:update---apiVersion: rbac.authorization.k8s.io/v1beta1kind: Rolemetadata:name: nginx-ingress-rolenamespace: ingress-nginxlabels:: ingress-nginx: ingress-nginxrules:apiGroups:""resources:configmapspodssecretsnamespacesverbs:getapiGroups:""resources:configmapsresourceNames:# Defaults to "<election-id>-<ingress-class>"# Here: "<ingress-controller-leader>-<nginx>"# This has to be adapted if you change either parameter# when launching the nginx-ingress-controller."ingress-controller-leader-nginx"verbs:getupdateapiGroups:""resources:configmapsverbs:createapiGroups:""resources:endpointsverbs:get---apiVersion: rbac.authorization.k8s.io/v1beta1kind: RoleBindingmetadata:name: nginx-ingress-role-nisa-bindingnamespace: ingress-nginxlabels:: ingress-nginx: ingress-nginxroleRef:apiGroup: rbac.authorization.k8s.iokind: Rolename: nginx-ingress-rolesubjects:kind: ServiceAccountname: nginx-ingress-serviceaccountnamespace: ingress-nginx---apiVersion: rbac.authorization.k8s.io/v1beta1kind: ClusterRoleBindingmetadata:name: nginx-ingress-clusterrole-nisa-bindinglabels:: ingress-nginx: ingress-nginxroleRef:apiGroup: rbac.authorization.k8s.iokind: ClusterRolename: nginx-ingress-clusterrolesubjects:kind: ServiceAccountname: nginx-ingress-serviceaccountnamespace: ingress-nginx---apiVersion: apps/v1kind: Deploymentmetadata:name: nginx-ingress-controllernamespace: ingress-nginxlabels:: ingress-nginx: ingress-nginxspec:replicas: 1selector:matchLabels:: ingress-nginx: ingress-nginxtemplate:metadata:labels:: ingress-nginx: ingress-nginxannotations:: "10254": "true"spec:hostNetwork: true# wait up to five minutes for the drain of connectionsterminationGracePeriodSeconds: 300serviceAccountName: nginx-ingress-serviceaccountnodeSelector:Ingress: nginx: linuxcontainers:name: nginx-ingress-controllerimage: quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.29.0args:/nginx-ingress-controller--configmap=$(POD_NAMESPACE)/nginx-configuration--tcp-services-configmap=$(POD_NAMESPACE)/tcp-services--udp-services-configmap=$(POD_NAMESPACE)/udp-services--publish-service=$(POD_NAMESPACE)/ingress-nginx--annotations-prefix=nginx.ingress.kubernetes.io--http-port=8080 # 如果你的master服务器已经安装了nginx，这里需要修改下，否则无法启动ingress-nginx服务--https-port=8443 # 同上securityContext:allowPrivilegeEscalation: truecapabilities:drop:ALLadd:NET_BIND_SERVICE# www-data -> 101runAsUser: 101env:name: POD_NAMEvalueFrom:fieldRef:fieldPath: metadata.namename: POD_NAMESPACEvalueFrom:fieldRef:fieldPath: metadata.namespaceports:name: httpcontainerPort: 80protocol: TCPname: httpscontainerPort: 443protocol: TCPlivenessProbe:failureThreshold: 3httpGet:path: /healthzport: 10254scheme: HTTPinitialDelaySeconds: 10periodSeconds: 10successThreshold: 1timeoutSeconds: 10readinessProbe:failureThreshold: 3httpGet:path: /healthzport: 10254scheme: HTTPperiodSeconds: 10successThreshold: 1timeoutSeconds: 10lifecycle:preStop:exec:command:/wait-shutdown---apiVersion: v1kind: LimitRangemetadata:name: ingress-nginxnamespace: ingress-nginxlabels:: ingress-nginx: ingress-nginxspec:limits:min:memory: 90Micpu: 100mtype: Container
参考文献：
https://blog.csdn.net/qq_37746855/article/details/116173976
https://blog.csdn.net/weixin_46152207/article/details/111355788
https://blog.csdn.net/catcher92/article/details/116207040
https://blog.51cto.com/u_14306186/2523096