感謝以下文章：
https://blog.csdn.net/wangchunfa122/article/details/86529406
https://blog.csdn.net/zw524362419/article/details/105353085
https://blog.csdn.net/wangkaizheng123/article/details/107491114
http://www.reibang.com/p/04f5b9791dc4?from=singlemessage
https://www.cnblogs.com/xiaoxuebiye/p/11256292.html
https://www.cnblogs.com/alamisu/p/10751418.html

master1,node1,node2
sudo比較隨意已骇，需要自己加

系統(tǒng)配置修改

3臺(tái)
禁用swap

sudo swapoff -a
sudo sed -i 's/.*swap.*/#&/' /etc/fstab
free -h

關(guān)閉防火墻

systemctl stop firewalld
systemctl disable firewalld

關(guān)閉iptables/ufw

sudo ufw disable 
sudo ufw status

禁用Selinux

apt-get update
sudo apt install selinux-utils
sudo setenforce 0

修改/etc/hostname

vim /etc/hostname
vim /etc/hosts

重啟系統(tǒng)

sudo reboot

安裝Docker

3臺(tái)

卸載舊版本

sudo apt-get remove docker docker-engine docker-ce docker.io

設(shè)置倉(cāng)庫(kù)

#更新 apt 包索引
sudo apt-get update
#安裝 apt 依賴包遗遵，用于通過(guò)HTTPS來(lái)獲取倉(cāng)庫(kù):
sudo apt-get install \
   apt-transport-https \
   ca-certificates \
   curl \
   gnupg-agent \
   software-properties-common
#添加 Docker 的官方 GPG 密鑰：
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
#設(shè)置穩(wěn)定版?zhèn)}庫(kù)
sudo add-apt-repository \
   "deb [arch=amd64] https://download.docker.com/linux/ubuntu \
  $(lsb_release -cs) \
  stable"
#安裝最新版本的 Docker Engine-Community 和 containerd
sudo apt-get update
sudo apt-get install docker-ce docker-ce-cli containerd.io
#安裝完成 檢驗(yàn)是否安裝成功
sudo docker version

安裝kubectl，kubelet本缠，kubeadm

在Master和Node節(jié)點(diǎn)分別執(zhí)行如下操作

#打開(kāi)apt源文件：
sudo vim /etc/apt/sources.list
#添加如下：
deb https://mirrors.aliyun.com/kubernetes/apt kubernetes-xenial main
#可能在 apt-get update 時(shí)會(huì)碰到  no pubkey 的問(wèn)題删铃，執(zhí)行：
curl https://mirrors.aliyun.com/kubernetes/apt/doc/apt-key.gpg | sudo apt-key add - 
#然后更新apt源：
sudo apt-get update

#安裝kube：
sudo apt-get install -y kubelet=1.18.0-00 kubeadm=1.18.0-00 kubectl=1.18.0-00

注意：這里改成1.18.0版本是為kubeadm init做的需求读处，也可以不加版本號(hào)峭跳，直接apt-get install -y kubelet kubeadm kubectl，但是由于沒(méi)有找到當(dāng)前最新版本-1.18.6的kubeadm init需要的鏡像侧漓，所以下載1.18.0版本锅尘。
安裝之后查看版本

kubelet --version

啟動(dòng)master節(jié)點(diǎn)

查詢需要的鏡像：

kubeadm config images list --kubernetes-version v1.18.0

拉取鏡像：

docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/kube-apiserver:v1.18.0 
docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/kube-controller-manager:v1.18.0 
docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/kube-scheduler:v1.18.0 
docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy:v1.18.0 
docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.2 
docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/etcd:3.4.3-0 
docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/coredns:1.6.7

給鏡像改名：

docker tag registry.cn-hangzhou.aliyuncs.com/google_containers/kube-apiserver:v1.18.0 k8s.gcr.io/kube-apiserver:v1.18.0
docker tag registry.cn-hangzhou.aliyuncs.com/google_containers/kube-controller-manager:v1.18.0 k8s.gcr.io/kube-controller-manager:v1.18.0
docker tag registry.cn-hangzhou.aliyuncs.com/google_containers/kube-scheduler:v1.18.0 k8s.gcr.io/kube-scheduler:v1.18.0
docker tag registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy:v1.18.0 k8s.gcr.io/kube-proxy:v1.18.0
docker tag registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.2 k8s.gcr.io/pause:3.2
docker tag registry.cn-hangzhou.aliyuncs.com/google_containers/etcd:3.4.3-0 k8s.gcr.io/etcd:3.4.3-0
docker tag registry.cn-hangzhou.aliyuncs.com/google_containers/coredns:1.6.7 k8s.gcr.io/coredns:1.6.7

此時(shí)，鏡像下載完成布蔗，可以啟動(dòng)master節(jié)點(diǎn)了：

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

最后一個(gè)自己的地址
成功后保存這條消息鉴象，其他節(jié)點(diǎn)加入時(shí)需要使用忙菠。

kubeadm join 192.168.202.139:6443 --token ivi39c.0zwio7t51vq3kqud \
    --discovery-token-ca-cert-hash sha256:4aa65fef89ebda957717f80ef38ba2414f9895c432f91e181e213d5f8726afca 

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

主節(jié)點(diǎn)生效

kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml

如果失敗，則

kubectl apply -f  kube-flannel.yml

kube-flannel.yml內(nèi)容如下：

---
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', 'NET_RAW']
  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/v1
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/v1
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
  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
      hostNetwork: true
      priorityClassName: system-node-critical
      tolerations:
      - operator: Exists
        effect: NoSchedule
      serviceAccountName: flannel
      initContainers:
      - name: install-cni
        image: quay.io/coreos/flannel:v0.13.1-rc1
        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.13.1-rc1
        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", "NET_RAW"]
        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

配置Node

在各個(gè)node節(jié)點(diǎn)執(zhí)行如下命令（對(duì)應(yīng)master配置返回的 kubeadm join命令）纺弊，加入master集群

kubeadm join 192.168.202.139:6443 --token ivi39c.0zwio7t51vq3kqud \
    --discovery-token-ca-cert-hash sha256:4aa65fef89ebda957717f80ef38ba2414f9895c432f91e181e213d5f8726afca 

在master查看nodes狀態(tài)牛欢，Node的狀態(tài)為NotReady
查看pod狀態(tài)，部分服務(wù)沒(méi)有正常啟動(dòng)淆游，原因是各個(gè)node也缺少鏡像傍睹，需要手動(dòng)下載，按照在master手動(dòng)下載鏡像的方式下載即可