k8s搭建部署3个节点服务器

最新推荐文章于 2024-07-20 13:32:05 发布

LZW_6688

最新推荐文章于 2024-07-20 13:32:05 发布

阅读量903

点赞数 1

文章标签： docker 运维 kubernetes

版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。

本文链接：https://blog.csdn.net/LZW_6688/article/details/120142808

版权

目录

一、环境准备

二、安装kubeadm，kubelet和kubectl

三、部署kubernetes Master

四、node节点加入集群

五、查看集群的状态

Init:ImagePullBackOff错误

swap分区没有关闭

没有coredns镜像

一、环境准备

硬件环境要求：CPU 2核 Memory 2G

软件环境要求：CentOS Linux release 8.3.2011

三台机器：

IP：192.168.10.188 主机名：master

IP：192.168.10.189 主机名：node1

IP：192.168.10.190 主机名：node2

三台服务器都要进行以下操作，所以主机名用localhost代替

#解决依赖关系
[root@localhost ~]# yum install -y yum-utils zlib zlib-devel openssl openssl-devel pcre pcre-devel gcc gcc-c++ autoconf automake make  psmisc  lsof  net-tools vim python3

#临时关闭防火墙
[root@localhost ~]# systemctl stop firewalld
#设置开机关闭防火墙
[root@localhost ~]# systemctl disable firewalld

#临时关闭selinux
[root@localhost ~]# setenforce 0
#永久关闭selinux
[root@localhost ~]# vim /etc/selinux/config
SELINUX=disabled    #将SELINUX设置成disabled

安装docker

#卸载旧版本
[root@localhost ~]# yum remove docker \
>                   docker-client \
>                   docker-client-latest \
>                   docker-common \
>                   docker-latest \
>                   docker-latest-logrotate \
>                   docker-logrotate \
>                   docker-engine

#安装yum-utils软件包（提供yum-config-manager应用程序）
[root@localhost ~]# yum install -y yum-utils

#配置加速源
[root@localhost ~]# yum-config-manager \
>     --add-repo \
>         http://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo


#安装docker，设置开机启动
[root@localhost ~]# yum install -y docker-ce docker-ce-cli containerd.io
[root@localhost ~]# systemctl start docker
[root@localhost ~]# systemctl enable docker

#配置docker使用systemd作为默认Cgroup驱动
[root@localhost ~]# cat <<EOF > /etc/docker/daemon.json
> {
>    "exec-opts": ["native.cgroupdriver=systemd"]
> }
> EOF

#重启docker
[root@localhost ~]# systemctl restart docker

#关闭swap分区
#临时关闭
[root@localhost ~]# swapoff -a 
#永久关闭
[root@localhost ~]# sed -i '/ swap / s/^\(.*\)$/#\1/g' /etc/fstab 

#重新命名主机
hostnamectl set-hostname master

hostnamectl set-hostname node1

hostnamectl set-hostname node2

使用 su - root 切换用户重新登陆

#每台机器上修改/etc/hosts文件

cat >> /etc/hosts << EOF 
192.168.0.188 master
192.168.0.189 node1
192.168.0.190 node2
EOF

二、安装kubeadm，kubelet和kubectl

每台服务器上都要安装

#添加kubernetes YUM软件源
[root@localhost ~]# 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

#安装kubeadm，kubelet和kubectl
[root@localhost ~]# yum install -y kubelet kubeadm kubectl

#设置开机自启
[root@localhost ~]# systemctl enable kubelet

三、部署kubernetes Master

#提前准备coredns:1.8.4的镜像，后面需要使用,需要在每台机器上下载镜像
[root@master ~]# docker pull  coredns/coredns:1.8.4
[root@master ~]# docker tag coredns/coredns:1.8.4 registry.aliyuncs.com/google_containers/coredns:v1.8.4

#初始化操作在master服务器上执行
[root@master ~]# kubeadm init \
> --apiserver-advertise-address=192.168.10.188 \
> --image-repository registry.aliyuncs.com/google_containers \
> --service-cidr=10.1.0.0/16 \
> --pod-network-cidr=10.244.0.0/16

...
Your Kubernetes control-plane 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

Alternatively, if you are the root user, you can run:

  export KUBECONFIG=/etc/kubernetes/admin.conf

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.10.188:6443 --token l9posz.ca7citx3ig5vpsqg \
	--discovery-token-ca-cert-hash sha256:7229c76950a7b82f64ff14a72c3ef81bad0f8f02c553861ff63f48b2904dd55e 


[root@master ~]# mkdir -p $HOME/.kube
[root@master ~]# sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
[root@master ~]# sudo chown $(id -u):$(id -g) $HOME/.kube/config

#在master服务器上执行
[root@node1 ~]# cat 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', '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-rc2
        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-rc2
        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

#部署flannel
[root@master ~]# kubectl apply -f kube-flannel.yml

#查看是否部署成功
[root@master ~]# ps aux|grep flannel
root       14365  0.2  2.0 1339652 36952 ?       Ssl  9月06   0:11 /opt/bin/flanneld --ip-masq --kube-subnet-mgr
root       45591  0.0  0.0  12344  1148 pts/0    S+   00:17   0:00 grep --color=auto flannel

四、node节点加入集群

[root@node1 ~]# kubeadm join 192.168.10.188:6443 --token l9posz.ca7citx3ig5vpsqg \
> --discovery-token-ca-cert-hash sha256:7229c76950a7b82f64ff14a72c3ef81bad0f8f02c553861ff63f48b2904dd55e

[root@node2 ~]# kubeadm join 192.168.10.188:6443 --token l9posz.ca7citx3ig5vpsqg \
> --discovery-token-ca-cert-hash sha256:7229c76950a7b82f64ff14a72c3ef81bad0f8f02c553861ff63f48b2904dd55e

This node has joined the cluster:
* Certificate signing request was sent to apiserver and a response was received.
* The Kubelet was informed of the new secure connection details.

Run 'kubectl get nodes' on the control-plane to see this node join the cluster.

五、查看集群的状态

#等待节点准备完毕，需要等待几分钟
[root@master ~]# kubectl get nodes
NAME     STATUS     ROLES                  AGE   VERSION
master   Ready      control-plane,master   63m   v1.22.1
node1    Ready      <none>                 10m   v1.22.1
node2    Ready      <none>                 12m   v1.22.1

[root@master ~]# kubectl get pod -n kube-system
NAME                             READY   STATUS    RESTARTS   AGE
coredns-7f6cbbb7b8-p7v7v         1/1     Running   0          67m
coredns-7f6cbbb7b8-qzdbr         1/1     Running   0          67m
etcd-master                      1/1     Running   0          67m
kube-apiserver-master            1/1     Running   0          67m
kube-controller-manager-master   1/1     Running   0          67m
kube-flannel-ds-fgk2n            1/1     Running   0          14m
kube-flannel-ds-sh2m4            1/1     Running   0          65m
kube-proxy-hcdjw                 1/1     Running   0          67m
kube-proxy-j5qgx                 1/1     Running   0          14m
kube-scheduler-master            1/1     Running   0          67m

Init:ImagePullBackOff错误

#查看具体的出错信息
[root@node1 ~]# kubectl describe pod kube-flannel-ds-p4nx9 --namespace=kube-system


Normal   BackOff    16m (x4 over 26m)    kubelet            Back-off pulling image "quay.io/coreos/flannel:v0.13.1-rc2"
  Warning  Failed     16m (x4 over 26m)    kubelet            Error: ImagePullBackOff
  Warning  Failed     6m21s (x2 over 16m)  kubelet            Failed to pull image "quay.io/coreos/flannel:v0.13.1-rc2": rpc error: code = Unknown desc = context canceled
  Warning  Failed     6m21s (x4 over 26m)  kubelet            Error: ErrImagePull
  Normal   Pulling    6m10s (x5 over 26m)  kubelet            Pulling image "quay.io/coreos/flannel:v0.13.1-rc2"

#手动拉取镜像
[root@node1 ~]# docker pull quay.io/coreos/flannel:v0.13.1-rc2
v0.13.1-rc2: Pulling from coreos/flannel
df20fa9351a1: Already exists 
0fbfec51320e: Already exists 
734a6c0a0c59: Already exists 
95bcce43aaee: Pull complete 
f5cb02651392: Pull complete 
071b96dd834b: Pull complete 
164ad1e8ed3f: Pull complete

#查看镜像
[root@node1 ~]# docker images
REPOSITORY                                                        TAG           IMAGE ID       CREATED        SIZE
registry.aliyuncs.com/google_containers/kube-apiserver            v1.22.1       f30469a2491a   2 weeks ago    128MB
registry.aliyuncs.com/google_containers/kube-scheduler            v1.22.1       aca5ededae9c   2 weeks ago    52.7MB
registry.aliyuncs.com/google_containers/kube-proxy                v1.22.1       36c4ebbc9d97   2 weeks ago    104MB
registry.aliyuncs.com/google_containers/kube-controller-manager   v1.22.1       6e002eb89a88   2 weeks ago    122MB
registry.aliyuncs.com/google_containers/etcd                      3.5.0-0       004811815584   2 months ago   295MB
coredns/coredns                                                   1.8.4         8d147537fb7d   3 months ago   47.6MB
registry.aliyuncs.com/google_containers/coredns                   v1.8.4        8d147537fb7d   3 months ago   47.6MB
registry.aliyuncs.com/google_containers/pause                     3.5           ed210e3e4a5b   5 months ago   683kB
quay.io/coreos/flannel                                            v0.13.1-rc2   dee1cac4dd20   7 months ago   64.3MB

#查看flannel启动成功
[root@node1 ~]# ps aux|grep flannel
root       14856  0.0  2.0 1265920 37932 ?       Ssl  20:54   0:00 /opt/bin/flanneld --ip-masq --kube-subnet-mgr
root       16946  0.0  0.0  12344  1028 pts/0    S+   20:59   0:00 grep --color=auto flannel

swap分区没有关闭

出现这种故障，swapoff -a关闭交换分区即可

没有coredns镜像

手动拉取镜像

#提前准备coredns:1.8.4的镜像，后面需要使用,需要在每台机器上下载镜像
[root@master ~]# docker pull  coredns/coredns:1.8.4
[root@master ~]# docker tag coredns/coredns:1.8.4 registry.aliyuncs.com/google_containers/coredns:v1.8.4

关注

1
点赞
踩
0

收藏

觉得还不错? 一键收藏
0
评论
k8s搭建部署3个节点服务器

[root@localhost ~]# yum install -y yum-utils zlib zlib-devel openssl openssl-devel pcre pcre-devel gcc gcc-c++ autoconf automake make psmisc lsof net-tools vim python3[root@localhost ~]# systemctl stop firewalld[root@localhost ~]# systemctl disable .
复制链接

扫一扫

评论

被折叠的条评论为什么被折叠?

到【灌水乐园】发言

查看更多评论

添加红包

成就一亿技术人!

hope_wisdom

发出的红包

实付元

使用余额支付

点击重新获取

扫码支付

钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。