Kubernetes--2 kubeadm安装

搭建K8S集群

上一个文章中简答了解到了Kubernetes，这次来说说K8S集群怎么搭建

---

---

搭建K8S环境平台规划

单master集群

---

单个master节点，然后管理多个node节点

多master集群

多个master节点，管理多个node节点，同时中间多了一个负载均衡的过程

服务器硬件配置要求

测试环境

master：2核4G 20G
node： 4核8G 40G

生产环境

master：8核16G 100G
node： 16核64G 200G

目前生产部署Kubernetes集群主要有两种方式

kubeadm

kubeadm是一个K8S部署工具，提供Kubeadm init和Kubeadm join，用于快速部署Kubernetes集群
官网地址：点击这里

二进制包

从github下载发行版的二进制包，手动部署每一个组件，组成Kubernetes集群。

Kubeadm降低部署门槛，但屏蔽了很多细节，遇到问题很难排查。如果想更容易可控，推荐使用二进制包部署Kubernetes集群，虽然手动部署麻烦点，期间可以学习很多工作原理，也有利于后期维护

Kubeadm部署集群

Kubeadm是官方社区推出的一个用于快速部署Kunernetes集群的工具，这个工具能通过两条指令完成一个kubernetes集群的部署：

 #创建一个Master节点
 kubeadm init 
 
 #将Node节点加入到当前集群中
 $ kubeadm join <Master节点的IP和端口> 

Kubeadm方式搭建K8S集群

使用kubeadm方式搭建K8s集群主要分为一下几步

准备三台虚拟机，同时安装操作系统CentOS 7.x
对三个安装之后的操作系统进行初始化操作
对三个节点安装docker、kubelet、kubeadm、kubectl
在master节点执行kubeadm init命令初始化集群
在node节点执行kubeadm join命令，把node节点添加到当前集群
配置CNI网络插件，用于节点之间的联通
通过拉取一个nginx进行测试，能否进行外网测试

安装要求

在开始之前，部署Kubernetes集群机器需要满足一下几个条件

一台或者多态机器，操作系统为CentOS 7.x。内核版本4.0以上
硬件配置：至少2GB内存，2颗CPU，硬盘30G
集群中所有的机器之间网络互通
可以访问外网，需要拉取镜像，如果服务器不能上网，需要提前下载镜像并且导入节点
禁止swap分区

准备环境

角色	IP
Master	192.168.2.73
Node01	192.168.2.71
Node02	192.168.2.72

开始在每台集群上执行下面的命令

# 关闭防火墙
systemctl stop firewalld
systemctl disable firewalld

#关闭selinux
##永久关闭
sed -i 's/enforcing/disabled/' /etc/selinux/config 
##临时关闭
setenforce 0

#关闭swap
##临时关闭
swapoff -a
##永久关闭
sed -ri 's/.*swap.*/#&/' /etc/fstab

#根据规划设置主机名
##Master
hostnamectl set-hostname k8s-master
##Node01
hostnamectl set-hostname k8s-node01
##Node02
hostnamectl set-hostname k8s-node02

#在master节点添加hosts
cat >> /etc/hosts << EOF
192.168.2.73 k8s-master
192.168.2.71 k8s-node01
192.168.2.72 k8s-node02
EOF

#将桥接的IPv4流量传递到itables的链
cat > /etc/sysctl.d/k8s.conf << EOF
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1
net.ipv4.ip_forward=1
EOF
# 刷新生效
sysctl --system

#同步时间
yum -y install ntpdate
ntpdate -u ntp1.aliyun.com 

#调整时区为 中国/上海
timedatectl set-timezone Asia/Shanghai

#将当前的UTC时间写入硬件时钟
timedatectl set-local-rtc 0

#重启依赖于系统时间的服务
systemctl restart rsyslog
systemctl restart crond

#关闭系统不需要的服务
systemctl stop postfix && systemctl disable postfix

安装Docker/kubeadm/kubelet

所有节点安装Docker/kubeadm/kubelet，Kubernetes默认CRI（容器运行时）为Docker，因此先安装Docker

安装Docker

首先配置Docker的阿里yum源

cat >/etc/yum.repos.d/docker.repo<<EOF
[docker-ce-edge]
name=Docker CE Edge - \$basearch
baseurl=https://mirrors.aliyun.com/docker-ce/linux/centos/7/\$basearch/edge
enabled=1
gpgcheck=1
gpgkey=https://mirrors.aliyun.com/docker-ce/linux/centos/gpg
EOF

安装docker

#yum安装
yum -y install docker-ce

#查看docker版本
docker --version

#启动docker
systemctl start docker
systemctl enable docker

配置docker的镜像源

cat >> /etc/docker/daemon.json << EOF
{
  "registry-mirrors": ["https://b9pmyelo.mirror.aliyuncs.com"]
}
EOF

重启docker

systemctl restart docker

添加kubernetes软件源

配置yum的k8s软件源
cat < /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

安装kubeadm，kubelet和kubectl

由于版本更新频繁，这里需要指定版本号部署

#安装kubelet、kubeadm、kubectl，同时指定版本
yum -y install kubelet-1.18.0 kubeadm-1.18.0 kubectl-1.18.0

#设置开机启动
systemctl enable kubelet

部署kubernets master节点

在192.168.2.73节点执行

kubeadm init --apiserver-advertise-address=192.168.2.73 --image-repository registry.aliyuncs.com/google_containers --kubernetes-version v1.18.0 --service-cidr=10.96.0.0/12 --pod-network-cidr=10.244.0.0/16

根据初始化提示，使用kubectl工具

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

目前只有一个master节点在运行了，但是还处于为准备状态
下面还需要在node节点执行其他命令，将node01和node02加入到我们的k8s集群里

加入kubernetes node

下面我们需要到node01和node02节点，执行下面的代码向集群添加新节点
执行kubeadm init 输出的kubeadm join命令：

##注意，以下的命令是在master初始化完成后，每个人的都不一样！！！需要复制自己生成的
kubeadm join 192.168.177.130:6443 --token 8j6ui9.gyr4i156u30y80xf \
    --discovery-token-ca-cert-hash sha256:eda1380256a62d8733f4bddf926f148e57cf9d1a3a58fb45dd6e80768af5a500

默认token有效期为24小时，当过期后，该token就不可用了。这时就需要重新创建token

kubeadm tolen create --print-join-command

当我们把两个节点都加进来后，我们就可以去Master节点执行是下面的命令查看情况

kubectl get node

部署CNI网络插件

上面的状态还是NotReday，下面需要部署网络插件，来进行联网访问

下载网络插件配置
wget https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml

没代理的可以复制一下内容

---
apiVersion: policy/v1beta1
kind: PodSecurityPolicy
metadata:
  name: psp.flannel.unprivileged
  annotations:
    seccomp.security.alpha.kubernetes.io/allowedProfileNames: docker/default
    seccomp.security.alpha.kubernetes.io/defaultProfileName: docker/default
    apparmor.security.beta.kubernetes.io/allowedProfileNames: runtime/default
    apparmor.security.beta.kubernetes.io/defaultProfileName: runtime/default
spec:
  privileged: false
  volumes:
    - configMap
    - secret
    - emptyDir
    - hostPath
  allowedHostPaths:
    - pathPrefix: "/etc/cni/net.d"
    - pathPrefix: "/etc/kube-flannel"
    - pathPrefix: "/run/flannel"
  readOnlyRootFilesystem: false
  # Users and groups
  runAsUser:
    rule: RunAsAny
  supplementalGroups:
    rule: RunAsAny
  fsGroup:
    rule: RunAsAny
  # Privilege Escalation
  allowPrivilegeEscalation: false
  defaultAllowPrivilegeEscalation: false
  # Capabilities
  allowedCapabilities: ['NET_ADMIN']
  defaultAddCapabilities: []
  requiredDropCapabilities: []
  # Host namespaces
  hostPID: false
  hostIPC: false
  hostNetwork: true
  hostPorts:
  - min: 0
    max: 65535
  # SELinux
  seLinux:
    # SELinux is unused in CaaSP
    rule: 'RunAsAny'
---
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:
  name: flannel
rules:
  - apiGroups: ['extensions']
    resources: ['podsecuritypolicies']
    verbs: ['use']
    resourceNames: ['psp.flannel.unprivileged']
  - apiGroups:
      - ""
    resources:
      - pods
    verbs:
      - get
  - apiGroups:
      - ""
    resources:
      - nodes
    verbs:
      - list
      - watch
  - apiGroups:
      - ""
    resources:
      - nodes/status
    verbs:
      - patch
---
kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:
  name: flannel
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: flannel
subjects:
- kind: ServiceAccount
  name: flannel
  namespace: kube-system
---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: flannel
  namespace: kube-system
---
kind: ConfigMap
apiVersion: v1
metadata:
  name: kube-flannel-cfg
  namespace: kube-system
  labels:
    tier: node
    app: flannel
data:
  cni-conf.json: |
    {
      "name": "cbr0",
      "cniVersion": "0.3.1",
      "plugins": [
        {
          "type": "flannel",
          "delegate": {
            "hairpinMode": true,
            "isDefaultGateway": true
          }
        },
        {
          "type": "portmap",
          "capabilities": {
            "portMappings": true
          }
        }
      ]
    }
  net-conf.json: |
    {
      "Network": "10.244.0.0/16",
      "Backend": {
        "Type": "vxlan"
      }
    }
---
apiVersion: apps/v1
kind: DaemonSet
metadata:
  name: kube-flannel-ds-amd64
  namespace: kube-system
  labels:
    tier: node
    app: flannel
spec:
  selector:
    matchLabels:
      app: flannel
  template:
    metadata:
      labels:
        tier: node
        app: flannel
    spec:
      affinity:
        nodeAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            nodeSelectorTerms:
              - matchExpressions:
                  - key: kubernetes.io/os
                    operator: In
                    values:
                      - linux
                  - key: kubernetes.io/arch
                    operator: In
                    values:
                      - amd64
      hostNetwork: true
      tolerations:
      - operator: Exists
        effect: NoSchedule
      serviceAccountName: flannel
      initContainers:
      - name: install-cni
        image: quay.io/coreos/flannel:v0.12.0-amd64
        command:
        - cp
        args:
        - -f
        - /etc/kube-flannel/cni-conf.json
        - /etc/cni/net.d/10-flannel.conflist
        volumeMounts:
        - name: cni
          mountPath: /etc/cni/net.d
        - name: flannel-cfg
          mountPath: /etc/kube-flannel/
      containers:
      - name: kube-flannel
        image: quay.io/coreos/flannel:v0.12.0-amd64
        command:
        - /opt/bin/flanneld
        args:
        - --ip-masq
        - --kube-subnet-mgr
        resources:
          requests:
            cpu: "100m"
            memory: "50Mi"
          limits:
            cpu: "100m"
            memory: "50Mi"
        securityContext:
          privileged: false
          capabilities:
            add: ["NET_ADMIN"]
        env:
        - name: POD_NAME
          valueFrom:
            fieldRef:
              fieldPath: metadata.name
        - name: POD_NAMESPACE
          valueFrom:
            fieldRef:
              fieldPath: metadata.namespace
        volumeMounts:
        - name: run
          mountPath: /run/flannel
        - name: flannel-cfg
          mountPath: /etc/kube-flannel/
      volumes:
        - name: run
          hostPath:
            path: /run/flannel
        - name: cni
          hostPath:
            path: /etc/cni/net.d
        - name: flannel-cfg
          configMap:
            name: kube-flannel-cfg
---
apiVersion: apps/v1
kind: DaemonSet
metadata:
  name: kube-flannel-ds-arm64
  namespace: kube-system
  labels:
    tier: node
    app: flannel
spec:
  selector:
    matchLabels:
      app: flannel
  template:
    metadata:
      labels:
        tier: node
        app: flannel
    spec:
      affinity:
        nodeAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            nodeSelectorTerms:
              - matchExpressions:
                  - key: kubernetes.io/os
                    operator: In
                    values:
                      - linux
                  - key: kubernetes.io/arch
                    operator: In
                    values:
                      - arm64
      hostNetwork: true
      tolerations:
      - operator: Exists
        effect: NoSchedule
      serviceAccountName: flannel
      initContainers:
      - name: install-cni
        image: quay.io/coreos/flannel:v0.12.0-arm64
        command:
        - cp
        args:
        - -f
        - /etc/kube-flannel/cni-conf.json
        - /etc/cni/net.d/10-flannel.conflist
        volumeMounts:
        - name: cni
          mountPath: /etc/cni/net.d
        - name: flannel-cfg
          mountPath: /etc/kube-flannel/
      containers:
      - name: kube-flannel
        image: quay.io/coreos/flannel:v0.12.0-arm64
        command:
        - /opt/bin/flanneld
        args:
        - --ip-masq
        - --kube-subnet-mgr
        resources:
          requests:
            cpu: "100m"
            memory: "50Mi"
          limits:
            cpu: "100m"
            memory: "50Mi"
        securityContext:
          privileged: false
          capabilities:
             add: ["NET_ADMIN"]
        env:
        - name: POD_NAME
          valueFrom:
            fieldRef:
              fieldPath: metadata.name
        - name: POD_NAMESPACE
          valueFrom:
            fieldRef:
              fieldPath: metadata.namespace
        volumeMounts:
        - name: run
          mountPath: /run/flannel
        - name: flannel-cfg
          mountPath: /etc/kube-flannel/
      volumes:
        - name: run
          hostPath:
            path: /run/flannel
        - name: cni
          hostPath:
            path: /etc/cni/net.d
        - name: flannel-cfg
          configMap:
            name: kube-flannel-cfg
---
apiVersion: apps/v1
kind: DaemonSet
metadata:
  name: kube-flannel-ds-arm
  namespace: kube-system
  labels:
    tier: node
    app: flannel
spec:
  selector:
    matchLabels:
      app: flannel
  template:
    metadata:
      labels:
        tier: node
        app: flannel
    spec:
      affinity:
        nodeAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            nodeSelectorTerms:
              - matchExpressions:
                  - key: kubernetes.io/os
                    operator: In
                    values:
                      - linux
                  - key: kubernetes.io/arch
                    operator: In
                    values:
                      - arm
      hostNetwork: true
      tolerations:
      - operator: Exists
        effect: NoSchedule
      serviceAccountName: flannel
      initContainers:
      - name: install-cni
        image: quay.io/coreos/flannel:v0.12.0-arm
        command:
        - cp
        args:
        - -f
        - /etc/kube-flannel/cni-conf.json
        - /etc/cni/net.d/10-flannel.conflist
        volumeMounts:
        - name: cni
          mountPath: /etc/cni/net.d
        - name: flannel-cfg
          mountPath: /etc/kube-flannel/
      containers:
      - name: kube-flannel
        image: quay.io/coreos/flannel:v0.12.0-arm
        command:
        - /opt/bin/flanneld
        args:
        - --ip-masq
        - --kube-subnet-mgr
        resources:
          requests:
            cpu: "100m"
            memory: "50Mi"
          limits:
            cpu: "100m"
            memory: "50Mi"
        securityContext:
          privileged: false
          capabilities:
             add: ["NET_ADMIN"]
        env:
        - name: POD_NAME
          valueFrom:
            fieldRef:
              fieldPath: metadata.name
        - name: POD_NAMESPACE
          valueFrom:
            fieldRef:
              fieldPath: metadata.namespace
        volumeMounts:
        - name: run
          mountPath: /run/flannel
        - name: flannel-cfg
          mountPath: /etc/kube-flannel/
      volumes:
        - name: run
          hostPath:
            path: /run/flannel
        - name: cni
          hostPath:
            path: /etc/cni/net.d
        - name: flannel-cfg
          configMap:
            name: kube-flannel-cfg
---
apiVersion: apps/v1
kind: DaemonSet
metadata:
  name: kube-flannel-ds-ppc64le
  namespace: kube-system
  labels:
    tier: node
    app: flannel
spec:
  selector:
    matchLabels:
      app: flannel
  template:
    metadata:
      labels:
        tier: node
        app: flannel
    spec:
      affinity:
        nodeAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            nodeSelectorTerms:
              - matchExpressions:
                  - key: kubernetes.io/os
                    operator: In
                    values:
                      - linux
                  - key: kubernetes.io/arch
                    operator: In
                    values:
                      - ppc64le
      hostNetwork: true
      tolerations:
      - operator: Exists
        effect: NoSchedule
      serviceAccountName: flannel
      initContainers:
      - name: install-cni
        image: quay.io/coreos/flannel:v0.12.0-ppc64le
        command:
        - cp
        args:
        - -f
        - /etc/kube-flannel/cni-conf.json
        - /etc/cni/net.d/10-flannel.conflist
        volumeMounts:
        - name: cni
          mountPath: /etc/cni/net.d
        - name: flannel-cfg
          mountPath: /etc/kube-flannel/
      containers:
      - name: kube-flannel
        image: quay.io/coreos/flannel:v0.12.0-ppc64le
        command:
        - /opt/bin/flanneld
        args:
        - --ip-masq
        - --kube-subnet-mgr
        resources:
          requests:
            cpu: "100m"
            memory: "50Mi"
          limits:
            cpu: "100m"
            memory: "50Mi"
        securityContext:
          privileged: false
          capabilities:
             add: ["NET_ADMIN"]
        env:
        - name: POD_NAME
          valueFrom:
            fieldRef:
              fieldPath: metadata.name
        - name: POD_NAMESPACE
          valueFrom:
            fieldRef:
              fieldPath: metadata.namespace
        volumeMounts:
        - name: run
          mountPath: /run/flannel
        - name: flannel-cfg
          mountPath: /etc/kube-flannel/
      volumes:
        - name: run
          hostPath:
            path: /run/flannel
        - name: cni
          hostPath:
            path: /etc/cni/net.d
        - name: flannel-cfg
          configMap:
            name: kube-flannel-cfg
---
apiVersion: apps/v1
kind: DaemonSet
metadata:
  name: kube-flannel-ds-s390x
  namespace: kube-system
  labels:
    tier: node
    app: flannel
spec:
  selector:
    matchLabels:
      app: flannel
  template:
    metadata:
      labels:
        tier: node
        app: flannel
    spec:
      affinity:
        nodeAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            nodeSelectorTerms:
              - matchExpressions:
                  - key: kubernetes.io/os
                    operator: In
                    values:
                      - linux
                  - key: kubernetes.io/arch
                    operator: In
                    values:
                      - s390x
      hostNetwork: true
      tolerations:
      - operator: Exists
        effect: NoSchedule
      serviceAccountName: flannel
      initContainers:
      - name: install-cni
        image: quay.io/coreos/flannel:v0.12.0-s390x
        command:
        - cp
        args:
        - -f
        - /etc/kube-flannel/cni-conf.json
        - /etc/cni/net.d/10-flannel.conflist
        volumeMounts:
        - name: cni
          mountPath: /etc/cni/net.d
        - name: flannel-cfg
          mountPath: /etc/kube-flannel/
      containers:
      - name: kube-flannel
        image: quay.io/coreos/flannel:v0.12.0-s390x
        command:
        - /opt/bin/flanneld
        args:
        - --ip-masq
        - --kube-subnet-mgr
        resources:
          requests:
            cpu: "100m"
            memory: "50Mi"
          limits:
            cpu: "100m"
            memory: "50Mi"
        securityContext:
          privileged: false
          capabilities:
             add: ["NET_ADMIN"]
        env:
        - name: POD_NAME
          valueFrom:
            fieldRef:
              fieldPath: metadata.name
        - name: POD_NAMESPACE
          valueFrom:
            fieldRef:
              fieldPath: metadata.namespace
        volumeMounts:
        - name: run
          mountPath: /run/flannel
        - name: flannel-cfg
          mountPath: /etc/kube-flannel/
      volumes:
        - name: run
          hostPath:
            path: /run/flannel
        - name: cni
          hostPath:
            path: /etc/cni/net.d
        - name: flannel-cfg
          configMap:
            name: kube-flannel-cfg

#添加
kubectl apply -f kube-flannel.yaml
##1首先下载v0.12.1-rc2-amd64 的镜像 链接.
##2导入镜像。3个节点都需要导入
docker load -i flannel.tar
##下载到本地，将image: quay.io/coreos/flannel:v0.12.1-rc2 替换为 image: quay.io/coreos/flannel:v0.12.1-rc2-amd6

##查看状态【kube-system是k8s中的最小单元】

kubectl get pod -n kube-system

运行完成后，我们查看状态发现，已经变成ready状态了

入过上述操作完成后，还存在某个节点处于NotReady状态，可以在Master节点删除

#master节点执行删除
kubectl delete node k8s-node01

#然后到k8s-node01节点进行重置
kubeadm reset
#重置完成后再次加入
kubeadm join 192.168.2.73:6334 --token jkcz0t.3c40t0bqqz5g8wsb \
    --discovery-token-ca-cert-hash sha256:eda1380256a62d8733f4bddf926f148e57cf9d1a3a58fb45dd6e80768af5a500

测试kubernetes集群

我们都知道K8s是容器化技术，他可以联网去下载镜像，用容器的方式进行启动

在kubernetes集群中创建一个pod，验证时候正常运行

#创建一个镜像是nginx的deployment
kubectl create deployment nginx --image=nginx
#查看状态
kubectl get pod

如果pod的状态是Running，表示已经成功运行了

下面需要将端口暴露出去，可以让外部访问

#暴露端口
kubectl expose deployment nginx --port=80 --type=NodePort
#查看对外的端口
kubectl get pod,svc

通过浏览器访问测试

http://192.168.2.73:30613

OK! 目前为止，我们已经用kubeadm搭建完成了一个单master的k8s集群

错误汇总

错误一

在执行Kubernets init方法的时候，出现这个问题

error execution phase preflight: [preflight] Some fatal errors occurred:
[ERROR NumCPU]: the number of available CPUs 1 is less than the required 2

是因为VMware设置的核数为1，而K8s需求的最低核心数应该是2，调整核数重启系统即可

错误二

我们在给node1节点使用 kubernetes join命令的时候，出现以下错误

error execution phase preflight: [preflight] Some fatal errors
occurred: [ERROR Swap]: running with swap on is not supported. Please
disable swap

错误原因是需要关闭swap

# 关闭swap
# 临时
 swapoff -a 
# 永久
 sed -ri 's/.*swap.*/#&/' /etc/fstab

错误三

在给node节点是使用库beadm join命令的时候，出现

The HTTP call equal to ‘curl -sSL http://localhost:10248/healthz’
failed with error: Get http://localhost:10248/healthz: dial tcp
[::1]:10248: connect: connection refused

解决方法，首先需要到master节点，创建一个文件

# 创建文件夹
mkdir /etc/systemd/system/kubelet.service.d

# 创建文件
vim /etc/systemd/system/kubelet.service.d/10-kubeadm.cond

# 添加一下内容
Environment="KUBELET_SYSTEM_PODS_ARGS=--pod-manifest-path=/etc/kubernetes/manifests --allow-privileged=true --fail-swap-on=false"

# 重置
kubeadm reset

然后删除刚刚创建的配置目录

rm -rf $HOME/.kube

在master节点重启初始化

kubeadm init --apiserver-advertise-address=192.168.2.73 --image-repository registry.aliyuncs.com/google_containers --kubernetes-version v1.18.0 --service-cidr=10.96.0.0/12 --pod-network-cidr=10.244.0.0/16

初始化完成在重新到node节点，执行kubeadm join命令加入集群。添加完成后，使用

kubectl get node

命令查看节点是否添加成功

错误四

在执行查看节点的时候，kubectl get node会出现问题

Unable to connect to the server: x509: certificate signed by unknown
authority (possibly because of “crypto/rsa: verification error” while
trying to verify candidate authority certificate “kubernetes”)

这是因为我们之前创建的配置文件还存在，就是这些配置

mkdir -p $HOME/.kube sudo cp -i /etc/kubernetes/admin.conf
$HOME/.kube/config sudo chown $(id-u):$(id -g) $HOME/.kube/config

解决方法，首先把配置文件删除

rm -rf $HOME/.kube

再重新执行一次

mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config

这个问题主要是因为在执行kubeadm reset的时候，没有把$HOME/.kube 给移除掉，再次创建时就会出现问题了

错误五

安装的时候，出现一下问题

Another app is currently holding the yum lock; waiting for it to exit…

是因为yum上锁，解决方法

yum -y install docker-ce

错误六

在node使用kubeadm join时，出现

[root@k8smaster ~]# kubeadm join 192.168.2.73:6443 --token
jkcz0t.3c40t0bqqz5g8wsb --discovery-token-ca-cert-hash
sha256:bc494eeab6b7bac64c0861da16084504626e5a95ba7ede7b9c2dc7571ca4c9e5
W1117 06:55:11.220907 11230 join.go:346] [preflight] WARNING:
JoinControlPane.controlPlane settings will be ignored when
control-plane flag is not set. [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/ error execution phase
preflight: [preflight] Some fatal errors occurred: [ERROR
FileContent–proc-sys-net-ipv4-ip_forward]:
/proc/sys/net/ipv4/ip_forward contents are not set to 1 [preflight] If
you know what you are doing, you can make a check non-fatal with
--ignore-preflight-errors=... To see the stack trace of this error
execute with --v=5 or higher

处于安全考虑，Linux系统默认是进行之数据包转发的，所谓转发即当主机拥有多于一块网卡时，其中一块收到数据包，根据数据包的目的ip地址将包发往本机另一块网卡，该网卡根据路由表继续发送数据包。这通常就是路由器所要实现的功能。也就是说是说 /proc/sys/net/ipv4/ip_forward 文件的值不支持转发

0：禁止
1：转发

所以只需要将值改成1即可

echo "1" > /proc/sys/net/ipv4/ip_forward

修改完成后，重新执行命令即可

错误七

在不关闭kubenetes相关服务的情况下，对kubernetes的master节点进行重启。启动后无法获取集群信息，输入命令报错

kubectl get node
The connection to the server <master>:6443 was refused - did you specify the right host or port?

处理思路：
1首先检查环境变量

env | grep -i kube

##如果是环境变量的问题
export KUBECONFIG=/etc/kubernetes/admin.conf
export $HOME/.kube/config

2 检查docker服务是否正常

systemctl status docker.service

3 检查kubelet服务时候正常

systemctl status kubelet.service

4 检查端口是否被监听

netstat -tlunp | grep 6443

5 检查防火墙状态

systemctl status firewalld.service

6 查看日志

journalctl -xeu kubelet

OK！ 就这篇就这样吧，欢迎各位同学大佬提出自己的意见，辛苦了！