centos7使用kubeadm部署k8s_centos7 kubeadm-CSDN博客

本文链接：https://blog.csdn.net/qq_43144842/article/details/144061201

一、主机配置

节点名称	ip地址	操作系统	配置
k8s-master	192.168.61.133	centos7.8+	2核cpu，2g内存，20g硬盘
k8s-node1	192.168.61.134	centos7.8+	2核cpu，2g内存，20g硬盘
k8s-node2	192.168.61.135	centos7.8+	2核cpu，2g内存，20g硬盘

二、环境初始化（三台机器都做）

2.1、设置主机名

对192.168.61.133的主机设置主机名:

hostnamectl set-hostname k8s-master

对192.168.61.134的主机设置主机名:

hostnamectl set-hostname k8s-node1

对192.168.61.135的主机设置主机名:

hostnamectl set-hostname k8s-node2

这里推荐使用MobaXterm连接工具可以同时操作多台机器同时执行命令：

2.2、关闭防火墙和禁止防火墙开机启动

关闭防火墙

systemctl stop firewalld

禁止防火墙开机启动

systemctl disable firewalld

2.3、设置主机名解析

cat >> /etc/hosts << EOF
192.168.61.133 k8s-master
192.168.61.134 k8s-node1
192.168.61.135 k8s-node2
EOF

主机名解析请修改成自己三台机器对应ip地址

2.4、时间同步

yum install ntpdate -y
ntpdate time.windows.com

如果centos7使用yum源有问题，请查看centos7替换阿里云yum源

2.5、关闭selinux

setenforce 0
sed -i 's/enforcing/disabled/' /etc/selinux/config

2.6、关闭swap分区

swapoff -a
sed -ri 's/.*swap.*/#&/' /etc/fstab

2.7、将桥接的ipv4流量传到iptables

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
vm.swappiness = 0
EOF

modprobe br_netfilter
sysctl --system

2.8、开启ipvs

yum -y install ipset ipvsadm

cat > /etc/sysconfig/modules/ipvs.modules <<EOF
#!/bin/bash
modprobe -- ip_vs
modprobe -- ip_vs_rr
modprobe -- ip_vs_wrr
modprobe -- ip_vs_sh
modprobe -- nf_conntrack_ipv4
EOF

chmod 755 /etc/sysconfig/modules/ipvs.modules && bash /etc/sysconfig/modules/ipvs.modules && lsmod | grep -e ip_vs -e nf_conntrack_ipv4

2.9、安装docker

wget https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo -O /etc/yum.repos.d/docker-ce.repo

yum -y install docker-ce-18.06.3.ce-3.el7

systemctl enable docker && systemctl start docker

设置docker镜像加速器，可使用本人镜像加速器，提供flannel网络插件镜像

本人镜像加速器：

https://4rauofb7.mirror.aliyuncs.com

sudo mkdir -p /etc/docker

sudo tee /etc/docker/daemon.json <<-'EOF'
{
  "exec-opts": ["native.cgroupdriver=systemd"],	
  "registry-mirrors": ["https://4rauofb7.mirror.aliyuncs.com"],	
  "live-restore": true,
  "log-driver":"json-file",
  "log-opts": {"max-size":"500m", "max-file":"3"},
  "storage-driver": "overlay2"
}
EOF

sudo systemctl daemon-reload
sudo systemctl restart docker

三、安装kubeadm、kubelet和kubectl（3台机器都做）

3.1、使用阿里云的yum源

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

3.2、安装kubeadm、kubelet和kubectl（版本为v1.18.0）

yum install -y kubelet-1.18.0 kubeadm-1.18.0 kubectl-1.18.0

修改docker驱动，手动编辑配置文件替换docker driver为systemd

vim /etc/sysconfig/kubelet

# 修改
KUBELET_EXTRA_ARGS="--cgroup-driver=systemd"
KUBE_PROXY_MODE="ipvs"

systemctl enable kubelet

四、安装master节点

部署k8s的master节点：

kubeadm init \
  --apiserver-advertise-address=192.168.61.133 \
  --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

根据提示消息执行：

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

五、安装node节点

对两台node节点机器分别执行加入集群命令（主节点初始化之后生成的命令）：

kubeadm join 192.168.61.133:6443 --token jv039y.bh8yetcpo6zeqfyj \
    --discovery-token-ca-cert-hash sha256:3c81e535fd4f8ff1752617d7a2d56c3b23779cf9545e530828c0ff6b507e0e26

token有效期为2小时，如果过期需要重新创建，重新创建命令：

kubeadm token create --print-join-command

六、部署CNI网络插件

这里选用flannel插件，kube-flannel.yml文件内容如下(镜像地址已替换本人阿里云镜像，记得使用上面本人docker镜像加速器)：

---
---
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-plugin
        image: crpi-76p8c80pxtcpef3f.cn-hangzhou.personal.cr.aliyuncs.com/sljflannel/flannel:flannel-cni-plugin-v1.0.0
        command:
        - cp
        args:
        - -f
        - /flannel
        - /opt/cni/bin/flannel
        volumeMounts:
        - name: cni-plugin
          mountPath: /opt/cni/bin
      - name: install-cni
        image: crpi-76p8c80pxtcpef3f.cn-hangzhou.personal.cr.aliyuncs.com/sljflannel/flannel:flannel-v0.15.1
        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: crpi-76p8c80pxtcpef3f.cn-hangzhou.personal.cr.aliyuncs.com/sljflannel/flannel:flannel-v0.15.1
        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-plugin
        hostPath:
          path: /opt/cni/bin
      - name: cni
        hostPath:
          path: /etc/cni/net.d
      - name: flannel-cfg
        configMap:
          name: kube-flannel-cfg

编辑写入上述文件内容，部署flannel插件（master节点执行）：

kubectl apply -f kube-flannel.yml

七、服务验证和部署

7.1、服务验证

查看pod运行状态：

kubectl get pods -n kube-system

7.2、nignx部署

部署nginx：

kubectl create deployment nginx --image=anolis-registry.cn-zhangjiakou.cr.aliyuncs.com/openanolis/nginx:1.14.1-8.6

暴露端口：

kubectl expose deployment nginx --port=80 --type=NodePort

查看服务：

kubectl get pods,svc

使用集群主机任意ip+service暴露的外部端口31208访问浏览器：