安装k8s Master高可用集群

最新推荐文章于 2024-08-13 15:35:52 发布
最新推荐文章于 2024-08-13 15:35:52 发布
阅读量339 收藏 1
点赞数
文章标签： json 后端 网络
原文链接：https://yq.aliyun.com/articles/679672
版权

安装k8s Master高可用集群

主机	          角色	            组件

172.18.6.101	K8S Master	Kubelet,kubectl,cni,etcd

172.18.6.102	K8S Master	Kubelet,kubectl,cni,etcd

172.18.6.103	K8S Master	Kubelet,kubectl,cni,etcd

172.18.6.104	K8S Worker	Kubelet,cni

172.18.6.105	K8S Worker	Kubelet,cni

172.18.6.106	K8S Worker	Kubelet,cni

etcd安装

保证k8smaster高可用，不建议使用container的方式启动etcd集群，因为container可能会 出现随时死掉的情况，etcd每个节点的启动service又是有状态的。因此此处将以二进制方式进行部署，建议在正式环境中最少部署3个节点的etcd集群，etcd具体安装步骤参考本地服务方式搭建etcd集群

必要组件以及证书安装

ca证书

参考kubernetes中证书生成创建CA证书，并将ca-key.pem与ca.pem放置到k8s集群中所有节点下的/etc/kubernetes/ssl下

woker证书制作

参考kubernetes中证书生成从节点证书生成段落，进行worker节点证书生成。对应ip的证书放置到对应worker节点的/etc/kubernetes/ssl下

kubelet.conf配置安装

创建/etc/kubernetes/kubelet.conf内容如下：

apiVersion: v1

kind: Config

clusters:

- name: local

  cluster:

    server: https://[负载均衡IP]:[apiserver端口]

    certificate-authority: /etc/kubernetes/ssl/ca.pem

users:

- name: kubelet

  user:

    client-certificate: /etc/kubernetes/ssl/worker.pem

    client-key: /etc/kubernetes/ssl/worker-key.pem

contexts:

- context:

    cluster: local

    user: kubelet

  name: kubelet-context

current-context: kubelet-context

cni插件安装

从containernetworking的cni项目中下载cni的必须二进制文件，需要放置到k8s集群中所有节点下的/opt/cni/bin下。

后续将提供rpm包进行一键安装。

kubelet服务部署

注意：后续将提供rpm包进行一键安装。

将对应版本的kubelet二进制文件放置到k8s集群中所有节点下的/usr/bin下

创建/etc/systemd/system/kubelet.service内容如下：

# /etc/systemd/system/kubelet.service

[Unit]

Description=kubelet: The Kubernetes Node Agent

Documentation=http://kubernetes.io/docs/


[Service]

Environment="KUBELET_KUBECONFIG_ARGS=--kubeconfig=/etc/kubernetes/kubelet.conf --require-kubeconfig=true"

Environment="KUBELET_SYSTEM_PODS_ARGS=--pod-manifest-path=/etc/kubernetes/manifests --allow-privileged=true"

Environment="KUBELET_NETWORK_ARGS=--network-plugin=cni --cni-conf-dir=/etc/cni/net.d --cni-bin-dir=/opt/cni/bin"

Environment="KUBELET_DNS_ARGS=--cluster-dns=10.100.0.10 --cluster-domain=cluster.local"

Environment="KUBELET_EXTRA_ARGS=--pod-infra-container-image=registry.aliyuncs.com/shenshouer/pause-amd64:3.0"

ExecStart=

ExecStart=/usr/bin/kubelet $KUBELET_KUBECONFIG_ARGS $KUBELET_SYSTEM_PODS_ARGS $KUBELET_NETWORK_ARGS $KUBELET_DNS_ARGS $KUBELET_EXTRA_ARGS

Restart=always

StartLimitInterval=0

RestartSec=10


[Install]

WantedBy=multi-user.target

创建如下目录：

/etc/kubernetes/

|-- kubelet.conf

|-- manifests

`-- ssl

   |-- ca-key.pem

   |-- ca.pem

   |-- worker.csr

   |-- worker-key.pem

   |-- worker-openssl.cnf

   `-- worker.pem

master组件安装

配置负载均衡

配置LVS使用VIP172.18.6.254指向后端172.18.6.101、172.18.6.102、172.18.6.103， 如需简单，则可使用nginx进行TCP4层的负载。

证书生成

openssl.cnf内容如下：

[req]

req_extensions = v3_req

distinguished_name = req_distinguished_name

[req_distinguished_name]

[ v3_req ]

basicConstraints = CA:FALSE

keyUsage = nonRepudiation, digitalSignature, keyEncipherment

subjectAltName = @alt_names

[alt_names]

DNS.1 = kubernetes

DNS.2 = kubernetes.default

DNS.3 = kubernetes.default.svc

DNS.4 = kubernetes.default.svc.cluster.local

DNS.5 = test.example.com.cn

IP.1 = 10.96.0.1

IP.2 = 172.18.6.101

IP.3 = 172.18.6.102

IP.3 = 172.18.6.103

IP.4 = 172.18.6.254

# 三个master的IP

IP.2 = 172.18.6.101

IP.3 = 172.18.6.102

IP.3 = 172.18.6.103

# LVS负载均衡的VIP

IP.4 = 172.18.6.254

# 可能会用到的负载均衡domain

DNS.5 = test.example.com.cn

证书生成具体步骤请参考kubernetes中证书生成 Master证书生成部分与Worker证书生成部分，生成后的证书需要放置到三台Master节点对应路径上

其他组件安装

Master节点上/etc/kubernetes/manifests下放置如下三个文件

kube-apiserver.manifest:

# /etc/kubernetes/manifests/kube-apiserver.manifest

{

  "kind": "Pod",

  "apiVersion": "v1",

  "metadata": {

    "name": "kube-apiserver",

    "namespace": "kube-system",

    "creationTimestamp": null,

    "labels": {

      "component": "kube-apiserver",

      "tier": "control-plane"

    }

  },

  "spec": {

    "volumes": [

      {

        "name": "k8s",

        "hostPath": {

          "path": "/etc/kubernetes"

        }

      },

      {

        "name": "certs",

        "hostPath": {

          "path": "/etc/ssl/certs"

        }

      }

    ],

    "containers": [

      {

        "name": "kube-apiserver",

        "image": "registry.aliyuncs.com.cn/shenshouer/kube-apiserver:v1.5.2",

        "command": [

          "kube-apiserver",

          "--insecure-bind-address=127.0.0.1",

          "--admission-control=NamespaceLifecycle,LimitRanger,ServiceAccount,PersistentVolumeLabel,DefaultStorageClass,ResourceQuota",

          "--service-cluster-ip-range=10.96.0.0/12",

          "--service-account-key-file=/etc/kubernetes/ssl/apiserver-key.pem",

          "--client-ca-file=/etc/kubernetes/ssl/ca.pem",

          "--tls-cert-file=/etc/kubernetes/ssl/apiserver.pem",

          "--tls-private-key-file=/etc/kubernetes/ssl/apiserver-key.pem",

          "--secure-port=6443",

          "--allow-privileged",

          "--advertise-address=[当前Master节点IP]",

          "--kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname",

          "--anonymous-auth=false",

          "--etcd-servers=http://127.0.0.1:2379"

        ],

        "resources": {

          "requests": {

            "cpu": "250m"

          }

        },

        "volumeMounts": [

          {

            "name": "k8s",

            "readOnly": true,

            "mountPath": "/etc/kubernetes/"

          },

          {

            "name": "certs",

            "mountPath": "/etc/ssl/certs"

          }

        ],

        "livenessProbe": {

          "httpGet": {

            "path": "/healthz",

            "port": 8080,

            "host": "127.0.0.1"

          },

          "initialDelaySeconds": 15,

          "timeoutSeconds": 15,

          "failureThreshold": 8

        }

      }

    ],

    "hostNetwork": true

  },

  "status": {}

}

kube-controller-manager.manifest


{

 "kind": "Pod",

 "apiVersion": "v1",

 "metadata": {

   "name": "kube-controller-manager",

   "namespace": "kube-system",

   "creationTimestamp": null,

   "labels": {

     "component": "kube-controller-manager",

     "tier": "control-plane"

   }

 },

 "spec": {

   "volumes": [

     {

       "name": "k8s",

       "hostPath": {

         "path": "/etc/kubernetes"

       }

     },

     {

       "name": "certs",

       "hostPath": {

         "path": "/etc/ssl/certs"

       }

     }

   ],

   "containers": [

     {

       "name": "kube-controller-manager",

       "image": "registry.aliyuncs.com/shenshouer/kube-controller-manager:v1.5.2",

       "command": [

         "kube-controller-manager",

         "--address=127.0.0.1",

         "--leader-elect",

         "--master=127.0.0.1:8080",

         "--cluster-name=kubernetes",

         "--root-ca-file=/etc/kubernetes/ssl/ca.pem",

         "--service-account-private-key-file=/etc/kubernetes/ssl/apiserver-key.pem",

         "--cluster-signing-cert-file=/etc/kubernetes/ssl/ca.pem",

         "--cluster-signing-key-file=/etc/kubernetes/ssl/ca-key.pem",

         "--insecure-experimental-approve-all-kubelet-csrs-for-group=system:kubelet-bootstrap",

         "--allocate-node-cidrs=true",

         "--cluster-cidr=10.244.0.0/16"

       ],

       "resources": {

         "requests": {

           "cpu": "200m"

         }

       },

       "volumeMounts": [

         {

           "name": "k8s",

           "readOnly": true,

           "mountPath": "/etc/kubernetes/"

         },

         {

           "name": "certs",

           "mountPath": "/etc/ssl/certs"

         }

       ],

       "livenessProbe": {

         "httpGet": {

           "path": "/healthz",

           "port": 10252,

           "host": "127.0.0.1"

         },

         "initialDelaySeconds": 15,

         "timeoutSeconds": 15,

         "failureThreshold": 8

       }

     }

   ],

   "hostNetwork": true

 },

 "status": {}

}



kube-scheduler.manifest


{

 "kind": "Pod",

 "apiVersion": "v1",

 "metadata": {

   "name": "kube-scheduler",

   "namespace": "kube-system",

   "creationTimestamp": null,

   "labels": {

     "component": "kube-scheduler",

     "tier": "control-plane"

   }

 },

 "spec": {

   "containers": [

     {

       "name": "kube-scheduler",

       "image": "registry.aliyuncs.com/shenshouer/kube-scheduler:v1.5.2",

       "command": [

         "kube-scheduler",

         "--address=127.0.0.1",

         "--leader-elect",

         "--master=127.0.0.1:8080"

       ],

       "resources": {

         "requests": {

           "cpu": "100m"

         }

       },

       "livenessProbe": {

         "httpGet": {

           "path": "/healthz",

           "port": 10251,

           "host": "127.0.0.1"

         },

         "initialDelaySeconds": 15,

         "timeoutSeconds": 15,

         "failureThreshold": 8

       }

     }

   ],

   "hostNetwork": true

 },

 "status": {}

其他组件安装

kube-proxy安装

在任意master上执行kubectl create -f kube-proxy-ds.yaml，其中kube-proxy-ds.yaml内容如下：

apiVersion: extensions/v1beta1

kind: DaemonSet

metadata:

  labels:

    component: kube-proxy

    k8s-app: kube-proxy

    kubernetes.io/cluster-service: "true"

    name: kube-proxy

    tier: node

  name: kube-proxy

  namespace: kube-system

spec:

  selector:

    matchLabels:

      component: kube-proxy

      k8s-app: kube-proxy

      kubernetes.io/cluster-service: "true"

      name: kube-proxy

      tier: node

  template:

    metadata:

      labels:

        component: kube-proxy

        k8s-app: kube-proxy

        kubernetes.io/cluster-service: "true"

        name: kube-proxy

        tier: node

    spec:

      containers:

      - command:

        - kube-proxy

        - --kubeconfig=/run/kubeconfig

        - --cluster-cidr=10.244.0.0/16

        image: registry.aliyuncs.com/shenshouer/kube-proxy:v1.5.2

        imagePullPolicy: IfNotPresent

        name: kube-proxy

        resources: {}

        securityContext:

          privileged: true

        terminationMessagePath: /dev/termination-log

        volumeMounts:

        - mountPath: /var/run/dbus

          name: dbus

        - mountPath: /run/kubeconfig

          name: kubeconfig

        - mountPath: /etc/kubernetes/ssl

          name: ssl

      dnsPolicy: ClusterFirst

      hostNetwork: true

      restartPolicy: Always

      securityContext: {}

      terminationGracePeriodSeconds: 30

      volumes:

      - hostPath:

          path: /etc/kubernetes/kubelet.conf

        name: kubeconfig

      - hostPath:

          path: /var/run/dbus

        name: dbus

      - hostPath:

          path: /etc/kubernetes/ssl

        name: ssl

网络组件安装

在任意master上执行kubectl apply -f kube-flannel.yaml，其中kube-flannel.yaml内容如下，注意，如果是在vagrant启动的虚拟机中运行，请修改flannled启动参数将--iface指向具体通讯网卡

---

apiVersion: v1

kind: ServiceAccount

metadata:

  name: flannel

  namespace: kube-system

---

kind: ConfigMap

apiVersion: v1

metadata:

  namespace: kube-system

  name: kube-flannel-cfg

  labels:

    tier: node

    app: flannel

data:

  cni-conf.json: |

    {

      "name": "cbr0",

      "type": "flannel",

      "delegate": {

        "ipMasq": true,

        "bridge": "cbr0",

        "hairpinMode": true,

        "forceAddress": true,

        "isDefaultGateway": true

      }

    }

  net-conf.json: |

    {

      "Network": "10.244.0.0/16",

      "Backend": {

        "Type": "vxlan"

      }

    }

---

apiVersion: extensions/v1beta1

kind: DaemonSet

metadata:

  namespace: kube-system

  name: kube-flannel-ds

  labels:

    tier: node

    app: flannel

spec:

  template:

    metadata:

      labels:

        tier: node

        app: flannel

    spec:

      hostNetwork: true

      nodeSelector:

        beta.kubernetes.io/arch: amd64

      serviceAccountName: flannel

      containers:

      - name: kube-flannel

        image: registry.aliyuncs.com/shenshouer/flannel:v0.7.0

        command: [ "/opt/bin/flanneld", "--ip-masq", "--kube-subnet-mgr", "--iface=eth0" ]

        securityContext:

          privileged: true

        env:

        - name: POD_NAME

          valueFrom:

            fieldRef:

              fieldPath: metadata.name

        - name: POD_NAMESPACE

          valueFrom:

            fieldRef:

              fieldPath: metadata.namespace

        volumeMounts:

        - name: run

          mountPath: /run

        - name: flannel-cfg

          mountPath: /etc/kube-flannel/

      - name: install-cni

        image: registry.aliyuncs.com/shenshouer/flannel:v0.7.0

        command: [ "/bin/sh", "-c", "set -e -x; cp -f /etc/kube-flannel/cni-conf.json /etc/cni/net.d/10-flannel.conf; while true; do sleep 3600; done" ]

        volumeMounts:

        - name: cni

          mountPath: /etc/cni/net.d

        - name: flannel-cfg

          mountPath: /etc/kube-flannel/

      volumes:

        - name: run

          hostPath:

            path: /run

        - name: cni

          hostPath:

            path: /etc/cni/net.d

        - name: flannel-cfg

          configMap:

            name: kube-flannel-cfg

DNS部署

在任意master上执行kubectl create -f skydns.yaml，其中skydns.yaml内容如下

apiVersion: v1

kind: Service

metadata:

  name: kube-dns

  namespace: kube-system

  labels:

    k8s-app: kube-dns

    kubernetes.io/cluster-service: "true"

    kubernetes.io/name: "KubeDNS"

spec:

  selector:

    k8s-app: kube-dns

  clusterIP: 10.100.0.10

  ports:

  - name: dns

    port: 53

    protocol: UDP

  - name: dns-tcp

    port: 53

    protocol: TCP


---

apiVersion: extensions/v1beta1

kind: Deployment

metadata:

  name: kube-dns

  namespace: kube-system

  labels:

    k8s-app: kube-dns

    kubernetes.io/cluster-service: "true"

spec:

  # replicas: not specified here:

  # 1. In order to make Addon Manager do not reconcile this replicas parameter.

  # 2. Default is 1.

  # 3. Will be tuned in real time if DNS horizontal auto-scaling is turned on.

  strategy:

    rollingUpdate:

      maxSurge: 10%

      maxUnavailable: 0

  selector:

    matchLabels:

      k8s-app: kube-dns

  template:

    metadata:

      labels:

        k8s-app: kube-dns

      annotations:

        scheduler.alpha.kubernetes.io/critical-pod: ''

        scheduler.alpha.kubernetes.io/tolerations: '[{"key":"CriticalAddonsOnly", "operator":"Exists"}]'

    spec:

      containers:

      - name: kubedns

        image: registry.aliyuncs.com/shenshouer/kubedns-amd64:1.9

        resources:

          # TODO: Set memory limits when we've profiled the container for large

          # clusters, then set request = limit to keep this container in

          # guaranteed class. Currently, this container falls into the

          # "burstable" category so the kubelet doesn't backoff from restarting it.

          limits:

            memory: 170Mi

          requests:

            cpu: 100m

            memory: 70Mi

        livenessProbe:

          httpGet:

            path: /healthz-kubedns

            port: 8080

            scheme: HTTP

          initialDelaySeconds: 60

          timeoutSeconds: 5

          successThreshold: 1

          failureThreshold: 5

        readinessProbe:

          httpGet:

            path: /readiness

            port: 8081

            scheme: HTTP

          # we poll on pod startup for the Kubernetes master service and

          # only setup the /readiness HTTP server once that's available.

          initialDelaySeconds: 3

          timeoutSeconds: 5

        args:

        - --domain=cluster.local.

        - --dns-port=10053

        - --config-map=kube-dns

        # This should be set to v=2 only after the new image (cut from 1.5) has

        # been released, otherwise we will flood the logs.

        - --v=0

        - --federations=myfederation=federation.test

        env:

        - name: PROMETHEUS_PORT

          value: "10055"

        ports:

        - containerPort: 10053

          name: dns-local

          protocol: UDP

        - containerPort: 10053

          name: dns-tcp-local

          protocol: TCP

        - containerPort: 10055

          name: metrics

          protocol: TCP

      - name: dnsmasq

        image: registry.aliyuncs.com/shenshouer/kube-dnsmasq-amd64:1.4

        livenessProbe:

          httpGet:

            path: /healthz-dnsmasq

            port: 8080

            scheme: HTTP

          initialDelaySeconds: 60

          timeoutSeconds: 5

          successThreshold: 1

          failureThreshold: 5

        args:

        - --cache-size=1000

        - --no-resolv

        - --server=127.0.0.1#10053

        - --log-facility=-

        ports:

        - containerPort: 53

          name: dns

          protocol: UDP

        - containerPort: 53

          name: dns-tcp

          protocol: TCP

        # see: https://github.com/kubernetes/kubernetes/issues/29055 for details

        resources:

          requests:

            cpu: 150m

            memory: 10Mi

      - name: dnsmasq-metrics

        image: registry.aliyuncs.com/shenshouer/dnsmasq-metrics-amd64:1.0

        livenessProbe:

          httpGet:

            path: /metrics

            port: 10054

            scheme: HTTP

          initialDelaySeconds: 60

          timeoutSeconds: 5

          successThreshold: 1

          failureThreshold: 5

        args:

        - --v=2

        - --logtostderr

        ports:

        - containerPort: 10054

          name: metrics

          protocol: TCP

        resources:

          requests:

            memory: 10Mi

      - name: healthz

        image: registry.aliyuncs.com/shenshouer/exechealthz-amd64:1.2

        resources:

          limits:

            memory: 50Mi

          requests:

            cpu: 10m

            # Note that this container shouldn't really need 50Mi of memory. The

            # limits are set higher than expected pending investigation on #29688.

            # The extra memory was stolen from the kubedns container to keep the

            # net memory requested by the pod constant.

            memory: 50Mi

        args:

        - --cmd=nslookup kubernetes.default.svc.cluster.local 127.0.0.1 >/dev/null

        - --url=/healthz-dnsmasq

        - --cmd=nslookup kubernetes.default.svc.cluster.local 127.0.0.1:10053 >/dev/null

        - --url=/healthz-kubedns

        - --port=8080

        - --quiet

        ports:

        - containerPort: 8080

          protocol: TCP

      dnsPolicy: Default  # Don't use cluster DNS.

Node节点安装

Docker安装

新建/etc/kubernetes/目录


|-- kubelet.conf

|-- manifests

`-- ssl

  |-- ca-key.pem

  |-- ca.pem

  |-- ca.srl

  |-- worker.csr

  |-- worker-key.pem

  |-- worker-openssl.cnf

  `-- worker.pem

新建/etc/kubernetes/kubelet.conf配置，参考kubelet.conf配置

新建/etc/kubernetes/ssl，证书制作参考worker证书制作

新建/etc/kubernetes/manifests

新建/opt/cni/bin,安装CNI参考cni安装步骤

安装kubelet,参考kubelet安装

systemctl enable kubelet && systemctl restart kubelet && journalctl -fu kubelet

本文转自CSDN-安装k8s Master高可用集群

weixin_33997389
关注
K8s（二十一）：在 Kubernetes 集群中部署 MySQL8.0 高可用集群（1主2从）
✨ 欢迎来到【Seal ^_^ 的CSDN博客】！这里是我记录技术心得、分享经验的地方。✨
04-16 1万+
🔴 K8s（二十一）：在 Kubernetes 集群中部署 MySQL8.0 高可用集群（1主2从）
二进制安装k8s 1.25.2 高可用集群
w975121565的博客
10-30 2067
二进制安装k8s 1.25.2 高可用集群
K8S高可用集群环境搭建
学无止境
12-24 1777
1.简介 本章节使用kubeadm搭建一套三主三从的高可用kubernetes集群。相比单master而言，多master更加有利于我们生产环境的稳定性。就算master节点宕机一台，我们依然有其他master节点保证我们的集群环境。多master节点需要依赖于keepalive还生成一个vip，也就是虚拟ip，做过nginx+keepalive的小伙伴们都知道，还需要一个haproxy来实现负载...
K8S集群Master高可用实践
weixin_34356310的博客
08-27 787
本文将在前文基础上介绍k8s集群的高可用实践，一般来讲，k8s集群高可用主要包含以下几个内容：1、etcd集群高可用2、集群dns服务高可用3、kube-apiserver、kube-controller-manager、kube-scheduler等master组件的高可用 其中etcd实现的办法较为容易，具体实现办法可参考前文：http://blog.51cto.com/ylw6006/20...
搭建高可用k8s集群
最新发布
qq_36838700的博客
08-13 1216
注意：标题中 没有标记（）的都是全部机器执行主机名称操作系统Centos 7Centos 7Centos 7Centos 7Centos 7内核版本IPNginx1.22.01.22.01.22.0————keepalived主从从————虚拟IP————
使用kubeadm搭建高可用的K8s集群_用来搭建k8s高可用集群_多master节点的具体过程.md
12-30
用来搭建k8s高可用集群,haproxy,keepalived,k8s高可用集群搭建过程
k8s高可用集群搭建
树袋熊
05-12 761
环境说明 [root@ha ~]# cat /etc/redhat-release CentOS Linux release 7.7.1908 (Core) 主机名 IP地址 说明 master-1 192.168.3.128 master-2 192.168.3.131 master-3 192.168.3.132 node-1 192.168.3.133 haprox主机 ha 192.168.3.134 haproxy主机 VIP 192.168.3.10
k8s-master 高可用
weixin_45081220的博客
09-29 536
准备工作安装 keepalived 和 HAProxy 并配置所有 Master 节点配置 KeepAlived，由于 KeepAlived 需要配置自身的IP地址和网卡名称，因此每个 KeepAlived 节点的配置都不一样所有 Master 节点配置 KeepAlived 健康检查文件所有节点启动HAProxy 和 KeepAlived测试 VIP 是否可用。
二进制部署k8s高可用集群（二进制-V1.20）.docx
06-29
二进制部署k8s高可用集群（二进制-V1.20） ...二进制部署k8s高可用集群需要准备好环境，部署 Etcd 集群，安装 Docker，实现高可用性等多个步骤。只有通过详细的步骤和配置，才能实现一个高可用的 K8s 集群。
K8S高可用集群架构实现
01-27
**K8S高可用集群架构实现** Kubernetes（K8S）是当前最流行的容器编排工具，它提供了一种高效、灵活的方式来管理和部署容器化应用程序。与早期的Docker Swarm相比，K8S提供了更高级别的抽象和自动化，使得应用的可...
【kubernetes】k8s高可用集群搭建（三主三从）
2302_77582029的博客
08-15 7432
【kubernetes】k8s高可用集群搭建（三主三从）
k8s-kubernetes--高可用集群的搭建
Gong_yz的博客
03-20 2100
k8s集群用到的高可用技术主要是keepalived和haproxy； keepalived：Keepalived主要是通过虚拟路由冗余来实现高可用功能；haproxy： haproxy 类似于nginx， 是一个负载均衡、反向代理软件。 nginx 采用master-workers 进程模型，每个进程单线程，多核CPU能充分利用。
k8s master 实现高可用
热门推荐
LoveSummer
11-16 2万+
k8s的高可用，主要是实现Master节点的高可用。那么我们看看各个组件是如何解决高可用的。：只工作在当前Node节点上，无需高可用。：etcd如果是放在集群内部的，在kubeadm1.5之后，对于多Master集群，一个Master节点加入集群后将自动实现集群化扩展。所以集群已经自动实现高可用，无需再人工干预。：对于多Master集群，这个组件只会有一个正常工作，其它处于休眠挂起状态。当工作节点发生故障时才会唤醒另一个接管。所以集群已经自动实现高可用，无需再人工干预。
搭建k8s高可用集群（Keepalived 和 HAproxy）
这里是火火火的世界
03-20 3664
spec:hosts:中每一行代表一个机器，要把所有机器列出来，name：实例的主机名（就是第一步准备工作时设置的hostname）,address和internalAddress是每个机器的IP地址，后面的user和password是能远程登录机器的用户名和密码。所有的master节点和worker工作节点配置docker镜像加速器（这里额外添加了docker的生产环境核心配置cgroup）使用如下命令在所有的master节点和worker工作节点安装docker并配置docker镜像加速器。
k8s–多master高可用集群环境搭建
wangy_0228的专栏
12-04 2443
Kubernetes 是一个可移植的、可扩展的 开源平台 ，用于 管理容器化的工作负载和服务，可促进声明式配置和自动化 。 Kubernetes 拥有一个庞大且快速增长的生态系统。Kubernetes 的服务、支持和工具广泛可用。
k8s系列(二)之k8s高可用集群环境搭建
qq_29653373的博客
08-03 1477
三、高可用k8s集群搭建(各节点间相互调用的高可用k8s都实现了，这里的高可用是指控制节点(主节点)实现负载均衡,一部分主节点宕机不影响对整个k8s的控制)1.1、网卡配置我的是ifcfg-eth0可根据实际网络情况配置自己的网络ip。2.2、Nginx配置（替换/etc/nginx/nginx.conf文件）1、控制节点基础配置(同时操作ip为7、8、9、11的主机)2.1、Nginx+keepalived的安装。2、控制节点(ip为7和8的主机)高可用配置。1.2、配置主机名和主机解析，注意。.....
部署企业级K8s高可用集群（kubeadm-V1.21）详细教程
本文将详细介绍如何部署一套完整的K8s高可用集群（kubeadm-V1.21）。在生产环境中，部署Kubernetes集群通常有两种方式，一种是使用kubeadm工具，另一种是从GitHub下载二进制包手动部署。本文将采用kubeadm搭建集群的...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

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

余额充值