Kubeadm的方式搭建K8s

部署K8S

1.准备工作

准备三个节点一个Master两个Node
hostnamectl set-hostname master
hostnamectl set-hostname node-01
hostnamectl set-hostname node-02

1.1免密 让master可以找到两个Node

ssh-keygen -t rsa
ssh-copy-id -i ~/.ssh/id_rsa.pub root@192.168.204.92
ssh-copy-id -i ~/.ssh/id_rsa.pub root@192.168.204.93

验证：ssh 192.168.204.92/93 date

1.2在Master和Node节点都装docker

安装docker
注意事项：
1.替换国内的源
wget -O /etc/yum.repos.d/CentOS-Base.repo http://mirrors.aliyun.com/repo/Centos-7.repo &> /dev/null
wget -O /etc/yum.repos.d/epel.repo http://mirrors.aliyun.com/repo/epel-7.repo &> /dev/null
yum clean all
yum makecache
2.服务器时区和时间保持国内
cp /usr/share/zoneinfo/Asia/Shanghai /etc/localtime
3.selinux和firewalld关闭
systemctl stop firewalld
4.内核版本3.10以上
5.ipv4转发
echo “net.ipv4.ip_forward = 1” >> /etc/sysctl.conf
安装
（1）安装依赖包
yum install -y yum-utils device-mapper-persistent-data lvm2
（2）添加docker软件包源
yum-config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo
（3）安装docker CE
yum install docker-ce-18.06.3.ce -y //这个版本最香
（4）启动
systemctl start docker
systemctl enable docker
（5）配置docker镜像加速器
在/etc/docker/daemon.json 中加入：
cat >>/etc/docker/daemon.json<< EOF
{
“registry-mirrors”: [“https://docker.mirrors.ustc.edu.cn/”]
}
EOF

1.3 hostname/hosts解析 所有节点

192.168.204.91 master
192.168.204.92 node1
192.168.204.93 node2

1.4 时间同步

被同步节点(master)：
sed -i ‘/^server/d’ /etc/chrony.conf
sed -i ‘2a server ntp2.aliyun.com iburst\nallow 10/8’ /etc/chrony.conf
systemctl restart chronyd.service
systemctl enable chronyd.service
同步节点(node)：
sed -i ‘/^server/d’ /etc/chrony.conf
sed -i ‘3i server 192.168.204.91 iburst’ /etc/chrony.conf
systemctl restart chronyd
systemctl enable chronyd.service

1.5 增加k8s阿里源//master/node

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=1
repo_gpgcheck=1
gpgkey=https://mirrors.aliyun.com/kubernetes/yum/doc/yum-key.gpg https://mirrors.aliyun.com/kubernetes/yum/doc/rpm-package-key.gpg
EOF

1.6 增加k8s转发配置并使其生效/master/node

/etc/sysctl.d/k8s.conf文件，添加如下内容：

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
执行命令使修改生效。
modprobe br_netfilter && sysctl -p /etc/sysctl.d/k8s.conf

1.7 内核参数优化/master/node

cat > /etc/sysctl.d/k8s.conf << EOF
net.ipv4.ip_forward = 1
net.bridge.bridge-nf-call-iptables = 1
net.bridge.bridge-nf-call-ip6tables = 1
fs.may_detach_mounts = 1
vm.overcommit_memory=1
vm.panic_on_oom=0
fs.inotify.max_user_watches=89100
fs.file-max=52706963
fs.nr_open=52706963
net.ipv4.tcp_keepalive_time = 600
net.ipv4.tcp.keepaliv.probes = 3
net.ipv4.tcp_keepalive_intvl = 15
net.ipv4.tcp.max_tw_buckets = 36000
net.ipv4.tcp_tw_reuse = 1
net.ipv4.tcp.max_orphans = 327680
net.ipv4.tcp_orphan_retries = 3
net.ipv4.tcp_syncookies = 1
net.ipv4.tcp_max_syn_backlog = 16384
net.ipv4.ip_conntrack_max = 65536
net.ipv4.tcp_max_syn_backlog = 16384
net.ipv4.top_timestamps = 0
net.core.somaxconn = 16384
EOF
立即生效
sysctl --system

1.8 安装ipvs并加载模块/master/node

yum install -y conntrack-tools ipvsadm ipset conntrack libseccomp
加载 IPVS 模块
cat > /etc/sysconfig/modules/ipvs.modules <<EOF
#!/bin/bash
ipvs_modules=“ip_vs ip_vs_lc ip_vs_wlc ip_vs_rr ip_vs_wrr ip_vs_lblc ip_vs_lblcr
ip_vs_dh ip_vs_sh ip_vs_fo ip_vs_nq ip_vs_sed ip_vs_ftp nf_conntrack”
for kernel_module in ${ipvs_modules}; do
/sbin/modinfo -F filename ${kernel_module} > /dev/null 2>&1
if [ $? -eq 0 ]; then
/sbin/modprobe ${kernel_module}
fi
done
EOF
chmod 755 /etc/sysconfig/modules/ipvs.modules && bash
/etc/sysconfig/modules/ipvs.modules && lsmod | grep ip_vs

1.9所有节点安装：

yum install -y kubelet-1.18.19 kubeadm-1.18.19 kubectl-1.18.19
所有节点设置kubelet开机自启：
systemctl enable kubelet.service

2 搭建k8s：

2.1拉取k8s所需镜像到本地master/slave：

docker pull registry.cn-shenzhen.aliyuncs.com/adifk8s/coredns:1.6.7
docker pull registry.cn-shenzhen.aliyuncs.com/adifk8s/pause:3.2
docker pull registry.cn-shenzhen.aliyuncs.com/adifk8s/etcd:3.4.3-0
docker pull registry.cn-shenzhen.aliyuncs.com/adifk8s/kube-controller-manager:v1.18.19
docker pull registry.cn-shenzhen.aliyuncs.com/adifk8s/api-server:v1.18.19
docker pull registry.cn-shenzhen.aliyuncs.com/adifk8s/kube-scheduler:v1.18.19
docker pull registry.cn-shenzhen.aliyuncs.com/adifk8s/kube-proxy:v1.18.19
registry.cn-shenzhen.aliyuncs.com/adifk8s

2.2 进行重新tag操作master/slave：

docker tag   registry.cn-shenzhen.aliyuncs.com/adifk8s/kube-proxy:v1.18.19  k8s.gcr.io/kube-proxy:v1.18.19
docker tag   registry.cn-shenzhen.aliyuncs.com/adifk8s/kube-scheduler:v1.18.19 k8s.gcr.io/kube-scheduler:v1.18.19
docker tag   registry.cn-shenzhen.aliyuncs.com/adifk8s/api-server:v1.18.19  k8s.gcr.io/kube-apiserver:v1.18.19
docker tag   registry.cn-shenzhen.aliyuncs.com/adifk8s/kube-controller-manager:v1.18.19  k8s.gcr.io/kube-controller-manager:v1.18.19
docker tag   registry.cn-shenzhen.aliyuncs.com/adifk8s/etcd:3.4.3-0  k8s.gcr.io/etcd:3.4.3-0
docker tag   registry.cn-shenzhen.aliyuncs.com/adifk8s/pause:3.2  k8s.gcr.io/pause:3.2
docker tag   registry.cn-shenzhen.aliyuncs.com/adifk8s/coredns:1.6.7  k8s.gcr.io/coredns:1.6.7
docker tag   registry.cn-shenzhen.aliyuncs.com/adifk8s/flannel:v0.14.0  k8s.gcr.io/flannel:v0.14.0

2.3 集群初始化

kubeadm init \
  --pod-network-cidr=10.244.0.0/16 \
  --apiserver-advertise-address=192.168.204.91

2.4 保存生成相关token，特别重要别弄丢（用于增加节点）：

kubeadm join 192.168.204.91:6443 --token owxzq1.2b2al52m1xgae3gd \
    --discovery-token-ca-cert-hash sha256:619193a0c5df198d9f342bbe6df5c373d82015188983bc5c21e4b9175cde334c 

2.5 按照输出做以下三步：

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

2.6 查看节点：

kubectl get node

状态Notready
检查（coredns是启动不了的状态，导致节点不可用，原因：因为网络插件没有安装，即flannel插件没有安装）
docker pull registry.cn-shenzhen.aliyuncs.com/adifk8s/flannel:v0.14.0
执行下面命令：
kubectl apply -f kube-flannel.yml 生成flannel

[root@master manifests]# cat 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', '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.14.0
        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: registry.cn-shenzhen.aliyuncs.com/adifk8s/flannel:v0.14.0
        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

2.7节点加入：

在node节点上执行如下命令

kubeadm join 192.168.204.91:6443 --token 7yoorb.zw1pqw67jprvq24b \
    --discovery-token-ca-cert-hash sha256:6c6586ec786fd0896978fadc09cb3a5f8bbba91e59d29f65b044a0c03890eedf 

如果node节点不可用，检查可能是flannel问题（如有flannel可先下载该镜像放入节点。）

如果过程中出需要重新初始化

1.驱逐节点，删除节点 /master

kubectl drain node-01 --delete-local-data --force --ignore-daemonsets
kubectl delete node node-01
kubectl drain node-02 --delete-local-data --force --ignore-daemonsets
kubectl delete node node-02
每个节点重置
kubeadm reset
然后重新初始化