Kubernetes 安装手册(非高可用版) 集群信息 1. 节点规划 部署k8s集群的节点按照用途可以划分为如下2类角色:
master :集群的master节点,集群的初始化节点,基础配置不低于2C4G
slave :集群的slave节点,可以多台,基础配置不低于2C4G
本例为了演示slave节点的添加,会部署一台master+2台slave ,节点规划如下:
主机名
节点ip
角色
部署组件
k8s-master
192.168.136.10
master
etcd, kube-apiserver, kube-controller-manager, kubectl, kubeadm, kubelet, kube-proxy, flannel
k8s-slave1
192.168.136.11
slave
kubectl, kubelet, kube-proxy, flannel
k8s-slave2
192.168.136.12
slave
kubectl, kubelet, kube-proxy, flannel
2. 组件版本
组件
版本
说明
CentOS
7.8.2003
Kernel
Linux 3.10.0-1062.9.1.el7.x86_64
etcd
3.3.15
使用容器方式部署,默认数据挂载到本地路径
coredns
1.6.2
kubeadm
v1.20.2
kubectl
v1.20.2
kubelet
v1.20.2
kube-proxy
v1.20.2
flannel
v0.11.0
安装前准备工作 1. 设置hosts解析 操作节点:所有节点(k8s-master,k8s-slave
)均需执行
修改hostname hostname必须只能包含小写字母、数字、”,”、”-“,且开头结尾必须是小写字母或数字1 2 3 4 5 6 7 8 $ hostnamectl set -hostname k8s-master $ hostnamectl set -hostname k8s-slave1 $ hostnamectl set -hostname k8s-slave2
添加hosts解析 1 2 3 4 5 $ cat >>/etc/hosts<<EOF 192.168 .26 .122 k8s-master192.168 .26 .123 k8s-slave1192.168 .26 .124 k8s-slave2EOF
2. 调整系统配置 操作节点: 所有的master和slave节点(k8s-master,k8s-slave
)需要执行
本章下述操作均以k8s-master为例,其他节点均是相同的操作(ip和hostname的值换成对应机器的真实值)
如果节点间无安全组限制(内网机器间可以任意访问),可以忽略,否则,至少保证如下端口可通: k8s-master节点:TCP:6443,2379,2380,60080,60081UDP协议端口全部打开 k8s-slave节点:UDP协议端口全部打开
设置iptables
1 iptables -P FORWARD ACCEPT
关闭swap
1 2 3 swapoff -a sed -i '/ swap / s/^\(.*\)$/#\1/g' /etc/fstab
关闭selinux和防火墙
1 2 3 sed -ri 's#(SELINUX=).*#\1disabled#' /etc/selinux/config setenforce 0 systemctl disable firewalld && systemctl stop firewalld
修改内核参数
1 2 3 4 5 6 7 8 cat <<EOF > /etc/sysctl.d/k8s.conf net.bridge.bridge-nf-call-ip6tables = 1 net.bridge.bridge-nf-call-iptables = 1 net.ipv4.ip_forward=1 vm.max_map_count=262144 EOF modprobe br_netfilter sysctl -p /etc/sysctl.d/k8s.conf
设置yum源
1 2 3 4 5 6 7 8 9 10 11 12 13 $ curl -o /etc/yum.repos.d/Centos-7 .repo http://mirrors.aliyun.com/repo/Centos-7 .repo$ curl -o /etc/yum.repos.d/docker-ce .repo http://mirrors.aliyun.com/docker-ce /linux/centos/docker-ce .repo$ cat <<EOF > /etc/yum.repos.d/kubernetes.repo[kubernetes ] name=Kubernetes baseurl=http://mirrors.aliyun.com/kubernetes/yum/repos/kubernetes-el7 -x86_64 enabled=1 gpgcheck=0 repo_gpgcheck=0 gpgkey=http://mirrors.aliyun.com/kubernetes/yum/doc/yum-key .gpg http://mirrors.aliyun.com/kubernetes/yum/doc/rpm-package -key .gpg EOF $ yum clean all && yum makecache
3. 安装docker 操作节点: 所有节点
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 $ yum list docker-ce --showduplicates | sort -r $ yum install docker-ce $ mkdir -p /etc/docker vi /etc/docker/daemon.json { "insecure-registries" : [ "192.168.136.10:5000" ], "registry-mirrors" : [ "你的镜像加速器地址" ] } $ systemctl enable docker && systemctl start docker
部署kubernetes 1. 安装 kubeadm, kubelet 和 kubectl 操作节点: 所有的master和slave节点(k8s-master,k8s-slave
) 需要执行
1 2 3 4 5 $ yum install -y kubelet-1 .20.2 kubeadm-1 .20.2 kubectl-1 .20.2 --disableexcludes =kubernetes$ kubeadm version$ systemctl enable kubelet
2. 初始化配置文件 操作节点: 只在master节点(k8s-master
)执行
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 $ kubeadm config print init-defaults > kubeadm.yaml $ cat kubeadm.yaml apiVersion: kubeadm.k8s.io/v1beta2 bootstrapTokens: - groups: - system:bootstrappers:kubeadm:default-node-token token: abcdef.0123456789abcdef ttl: 24h0m0s usages: - signing - authentication kind: InitConfiguration localAPIEndpoint: advertiseAddress: 192.168 .136 .10 bindPort: 6443 nodeRegistration: criSocket: /var/run/dockershim.sock name: k8s-master taints: - effect: NoSchedule key: node-role.kubernetes.io/master --- apiServer: timeoutForControlPlane: 4m0s apiVersion: kubeadm.k8s.io/v1beta2 certificatesDir: /etc/kubernetes/pki clusterName: kubernetes controllerManager: {}dns: type: CoreDNS etcd: local: dataDir: /var/lib/etcd imageRepository: registry.aliyuncs.com/google_containers kind: ClusterConfiguration kubernetesVersion: v1.20.2 networking: dnsDomain: cluster.local podSubnet: 10.244 .0 .0 /16 serviceSubnet: 10.96 .0 .0 /12 scheduler: {}
对于上面的资源清单的文档比较杂,要想完整了解上面的资源对象对应的属性,可以查看对应的 godoc 文档,地址: https://godoc.org/k8s.io/kubernetes/cmd/kubeadm/app/apis/kubeadm/v1beta2。
3. 提前下载镜像 操作节点:只在master节点(k8s-master
)执行
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 $ kubeadm config images list --config kubeadm.yaml registry.aliyuncs.com/google_containers/kube-apiserver:v1.20 .2 registry.aliyuncs.com/google_containers/kube-controller-manager:v1.20 .2 registry.aliyuncs.com/google_containers/kube-scheduler:v1.20 .2 registry.aliyuncs.com/google_containers/kube-proxy:v1.20 .2 registry.aliyuncs.com/google_containers/pause:3.1 registry.aliyuncs.com/google_containers/etcd:3.3 .15 -0 registry.aliyuncs.com/google_containers/coredns:1.6 .2 $ kubeadm config images pull --config kubeadm.yaml [config/images] Pulled registry.aliyuncs.com/google_containers/kube-apiserver:v1.20 .2 [config/images] Pulled registry.aliyuncs.com/google_containers/kube-controller-manager:v1.20 .2 [config/images] Pulled registry.aliyuncs.com/google_containers/kube-scheduler:v1.20 .2 [config/images] Pulled registry.aliyuncs.com/google_containers/kube-proxy:v1.20 .2 [config/images] Pulled registry.aliyuncs.com/google_containers/pause:3.1 [config/images] Pulled registry.aliyuncs.com/google_containers/etcd:3.3 .15 -0 [config/images] Pulled registry.aliyuncs.com/google_containers/coredns:1.6 .2
重要更新:如果出现不可用的情况,请使用如下方式来代替:
还原kubeadm.yaml的imageRepository
1 2 3 4 5 6 7 8 9 10 11 12 13 ... imageRepository: k8s.gcr.io ... kubeadm config images list --config kubeadm.yaml k8s.gcr.io/kube-apiserver:v1.20.2 k8s.gcr.io/kube-controller-manager:v1.20.2 k8s.gcr.io/kube-scheduler:v1.20.2 k8s.gcr.io/kube-proxy:v1.20.2 k8s.gcr.io/pause:3.1 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2
使用docker hub中的镜像源来下载,注意上述列表中要加上处理器架构,通常我们使用的虚拟机都是amd64
1 2 3 4 $ docker pull mirrorgooglecontainers/kube-scheduler -amd64 :v1.20.2 $ docker pull mirrorgooglecontainers/etcd-amd64 :3.3 .15 -0 ... $ docker tag mirrorgooglecontainers/etcd-amd64 :3.3 .15 -0 k8s.gcr.io/etcd:3.3 .15 -0
4. 初始化master节点 操作节点:只在master节点(k8s-master
)执行
1 kubeadm init --config kubeadm.yaml
若初始化成功后,最后会提示如下信息:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 ... Your Kubernetes master 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 .136 .10 :6443 --token abcdef.0123456789 abcdef \ --discovery-token-ca-cert-hash sha256:1c4305f032f4bf534f628c32f5039084f4b103c922ff71b12a5f0f98d1ca9a4f
接下来按照上述提示信息操作,配置kubectl客户端的认证
1 2 3 mkdir -p $HOME/.kube sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config sudo chown $(id -u):$(id -g) $HOME/.kube/config
⚠️注意: 此时使用 kubectl get nodes查看节点应该处于notReady状态,因为还未配置网络插件
若执行初始化过程中出错,根据错误信息调整后,执行kubeadm reset后再次执行init操作即可
5. 添加slave节点到集群中 操作节点:所有的slave节点(k8s-slave
)需要执行 在每台slave节点,执行如下命令,该命令是在kubeadm init成功后提示信息中打印出来的,需要替换成实际init后打印出的命令。
1 2 kubeadm join 192.168 .136 .10 :6443 --token abcdef.0123456789 abcdef \ --discovery-token-ca-cert-hash sha256:1c4305f032f4bf534f628c32f5039084f4b103c922ff71b12a5f0f98d1ca9a4f
如果忘记了此 token ,可以执行:kubeadm token create –print-join-command –ttl 0 ,再次查看 join 命令
6. 安装flannel插件 操作节点:只在master节点(k8s-master
)执行
1 wget https://raw.githubusercontent.com/coreos/flannel/2140 ac876ef134e0ed5af15c65e414cf26827915/Documentation/kube-flannel .yml
修改配置,指定网卡名称,大概在文件的190行,添加一行配置:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 $ vi kube-flannel .yml... containers: - name: kube-flannel image: quay.io/coreos/flannel:v0.11.0 -amd64 command: - /opt/bin/flanneld args: - --ip -masq - --kube -subnet -mgr - --iface =eth0 resources: requests: cpu: "100m" ...
(可选)修改flannel镜像地址,以防默认的镜像拉取失败,同样是在170和190行上下的位置
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 vi kube-flannel .yml ... containers: - name: kube-flannel image: 192.168 .136.10 :5000 /flannel:v0.11.0 -amd64 command: - /opt/bin/flanneld args: - --ip -masq - --kube -subnet -mgr - --iface =ens33 resources: requests: cpu: "100m" ...
1 2 3 4 $ docker pull quay.io/coreos/flannel:v0.11.0 -amd64 $ kubectl create -f kube-flannel .yml
1 2 3 4 # 拉去配置文件 curl https://docs.projectcalico.org/manifests/calico.yaml -O # 创建 calico kubectl apply -f calico.yaml
coredns 停滞再 Pending 状态:
这一行为是预期之中 ,因为系统就是这么设计的。 kubeadm 的网络供应商是中立的,因此管理员应该选择安装 pod 的网络插件 。必须完成 pod 的网络配置,然后才能完全部署Coredns。再网络被配置好之前,DNS 组件会一直处于 pending 状态
7. 设置master节点是否可调度(可选) 操作节点:k8s-master
默认部署成功后,master节点无法调度业务pod,如需设置master节点也可以参与pod的调度,需执行:
1 $ kubectl taint node k8s-master node-role.kubernetes.io/master:NoSchedule-
8. 验证集群 操作节点: 在master节点(k8s-master
)执行
创建测试nginx服务
1 $ kubectl run test-nginx --image=nginx:alpine
查看pod是否创建成功,并访问pod ip测试是否可用
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 $ kubectl get po -o wideNAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES test-nginx -5bd8859b98 -5nnnw 1 /1 Running 0 9 s 10.244 .1.2 k8s-slave1 <none> <none>$ curl 10.244 .1.2 ... <h1>Welcome to nginx!</h1> <p>If you see this page, the nginx web server is successfully installed and working. Further configuration is required.</p> <p>For online documentation and support please refer to <a href="http://nginx.org/" >nginx.org</a>.<br/> Commercial support is available at <a href="http://nginx.com/" >nginx.com</a>.</p> <p><em>Thank you for using nginx.</em></p> </body> </html>
9. 部署dashboard
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 $ wget https://raw.githubusercontent.com/kubernetes/dashboard/v2.0.0 -rc5 /aio/deploy/recommended.yaml$ vi recommended.yaml...... kind: Service apiVersion: v1 metadata: labels: k8s-app : kubernetes-dashboard name: kubernetes-dashboard namespace: kubernetes-dashboard spec: ports: - port: 443 targetPort: 8443 selector: k8s-app : kubernetes-dashboard type : NodePort ......
1 2 3 4 5 kubectl create -f recommended.yaml kubectl -n kubernetes-dashboard get svc NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE dashboard-metrics -scraper ClusterIP 10.105 .62.124 <none> 8000 /TCP 31 m kubernetes-dashboard NodePort 10.103 .74.46 <none> 443 :30133 /TCP 31 m
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 $ vi admin.confkind: ClusterRoleBinding apiVersion: rbac.authorization.k8s.io/v1beta1 metadata: name: admin annotations: rbac.authorization.kubernetes.io/autoupdate: "true" roleRef: kind: ClusterRole name: cluster-admin apiGroup: rbac.authorization.k8s.io subjects: - kind: ServiceAccount name: admin namespace: kubernetes-dashboard --- apiVersion: v1 kind: ServiceAccount metadata: name: admin namespace: kubernetes-dashboard $ kubectl create -f admin.conf$ kubectl -n kubernetes-dashboard get secret |grep admin-token admin-token -fqdpf kubernetes.io/service-account -token 3 7 m17s $ kubectl -n kubernetes-dashboard get secret admin-token -fqdpf -o jsonpath={.data.token}|base64 -d eyJhbGciOiJSUzI1NiIsImtpZCI6Ik1rb2xHWHMwbWFPMjJaRzhleGRqaExnVi1BLVNRc2txaEhETmVpRzlDeDQifQ.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJrdWJlcm5ldGVzLWRhc2hib2FyZCIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VjcmV0Lm5hbWUiOiJhZG1pbi10b2tlbi1mcWRwZiIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VydmljZS1hY2NvdW50Lm5hbWUiOiJhZG1pbiIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VydmljZS1hY2NvdW50LnVpZCI6IjYyNWMxNjJlLTQ1ZG...
10. 部署 ingress 官方文档
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 wget https://raw.githubusercontent.com/kubernetes/ingress-nginx /nginx-0 .30.0 /deploy/static /mandatory.yaml$ grep -n5 nodeSelector mandatory.yaml212 - spec:213 - hostNetwork: true 214 - 215 - terminationGracePeriodSeconds: 300 216 - serviceAccountName: nginx-ingress -serviceaccount 217 : nodeSelector:218 - ingress: "true" 219 - containers:220 - - name: nginx-ingress -controller 221 - image: quay.io/kubernetes-ingress -controller /nginx-ingress -controller :0.30 .0 222 - args:
创建 ingress
1 2 3 4 5 6 7 8 # 为k8s-master节点添加label $ kubectl label node k8s-master ingress=true $ kubectl apply -f mandatory.yaml # 查看 并 删除label kubectl get nodes --show-labels kubectl label nodes k8s-master ingress-
11. 清理环境 如果你的集群安装过程中遇到了其他问题,我们可以使用下面的命令来进行重置:
1 2 3 4 $ kubeadm reset$ ifconfig cni0 down && ip link delete cni0$ ifconfig flannel.1 down && ip link delete flannel.1 $ rm -rf /var/lib/cni/
12. 修改证书到期时间 使用kubeadm安装的集群,证书默认有效期为1年,可以通过如下方式修改为10年。
1 2 3 4 5 6 7 8 9 10 11 12 $ cd /etc/kubernetes/pki # 查看当前证书有效期 $ for i in $(ls *.crt); do echo "===== $i ====="; openssl x509 -in $i -text -noout | grep -A 3 'Validity' ; done $ mkdir backup_key; cp -rp ./* backup_key/ $ git clone https://github.com/yuyicai/update-kube-cert.git $ cd update-kube-cert/ $ bash update-kubeadm-cert.sh all # 重建管理服务 $ kubectl -n kube-system delete po kube-apiserver-k8s-master kube-controller-manager-k8s-master kube-scheduler-k8s-master
13. kubectl 配置命令自动补全 1 2 3 4 5 6 7 8 # 安装 bash 命令行自动补全扩展包 yum -y install bash-completion source /usr/share/bash-completion/bash_completion # 加载 kubectl completion source <(kubectl completion bash) # 临时生效 echo "source <(kubectl completion bash)" >> ~/.bashrc # 当前用户永久生效 source ~/.bashrc