2. 程式人生 > >kubeadm安裝kubernetes 1.13.2多master高可用集群

kubeadm安裝kubernetes 1.13.2多master高可用集群

阿新 • • 發佈：2019-02-15
nonlocal lap done mkdir -p cati waiting alived str token

1. 簡介

Kubernetes v1.13版本發布後，kubeadm才正式進入GA，可以生產使用,用kubeadm部署kubernetes集群也是以後的發展趨勢。目前Kubernetes的對應鏡像倉庫，在國內阿裏雲也有了鏡像站點，使用kubeadm部署Kubernetes集群變得簡單並且容易了很多，本文使用kubeadm帶領大家快速部署Kubernetes v1.13.2版本。

註意：請不要把目光僅僅放在部署上，如果你是新手，推薦先熟悉用二進制文件部署後，再來學習用kubeadm部署。二進制文件部署請查看我博客的其他文章。

2. 架構信息

系統版本：CentOS 7.6
內核：3.10.0-957.el7.x86_64
Kubernetes: v1.13.2
Docker-ce: 18.06
推薦硬件配置：2核2G

Keepalived保證apiserever服務器的IP高可用
Haproxy實現apiserver的負載均衡

為了減少服務器數量，haproxy、keepalived配置在node-01和node-02。

節點名稱 角色 IP 安裝軟件
負載VIP VIP 10.31.90.200
node-01 master 10.31.90.201 kubeadm、kubelet、kubectl、docker、haproxy、keepalived
node-02 master 10.31.90.202 kubeadm、kubelet、kubectl、docker、haproxy、keepalived
node-03 master 10.31.90.203 kubeadm、kubelet、kubectl、docker
node-04 node 10.31.90.204 kubeadm、kubelet、kubectl、docker
node-05 node 10.31.90.205 kubeadm、kubelet、kubectl、docker
node-06 node 10.31.90.206 kubeadm、kubelet、kubectl、docker
service網段 10.245.0.0/16

2.部署前準備工作

1) 關閉selinux和防火墻

sed -ri ‘s#(SELINUX=).*#\1disabled#‘ /etc/selinux/config
setenforce 0
systemctl disable firewalld
systemctl stop firewalld

2) 關閉swap

swapoff -a

3) 為每臺服務器添加host解析記錄

cat >>/etc/hosts<<EOF
10.31.90.201 node-01
10.31.90.202 node-02
10.31.90.203 node-03
10.31.90.204 node-04
10.31.90.205 node-05
10.31.90.206 node-06
EOF

4) 創建並分發密鑰

在node-01創建ssh密鑰。

[root@node-01 ~]# ssh-keygen -t rsa
Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa): 
Created directory ‘/root/.ssh‘.
Enter passphrase (empty for no passphrase): 
Enter same passphrase again: 
Your identification has been saved in /root/.ssh/id_rsa.
Your public key has been saved in /root/.ssh/id_rsa.pub.
The key fingerprint is:
SHA256:26z6DcUarn7wP70dqOZA28td+K/erv7NlaJPLVE1BTA root@node-01
The key‘s randomart image is:
+---[RSA 2048]----+
|            E..o+|
|             .  o|
|               . |
|         .    .  |
|        S o  .   |
|      .o X   oo .|
|       oB +.o+oo.|
|       .o*o+++o+o|
|     .++o+Bo+=B*B|
+----[SHA256]-----+

分發node-01的公鑰，用於免密登錄其他服務器

for n in `seq -w 01 06`;do ssh-copy-id node-$n;done

5) 配置內核參數

cat <<EOF >  /etc/sysctl.d/k8s.conf
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1
net.ipv4.ip_nonlocal_bind = 1
net.ipv4.ip_forward = 1
vm.swappiness=0
EOF

sysctl --system

6) 加載ipvs模塊

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

7) 添加yum源

cat << EOF > /etc/yum.repos.d/kubernetes.repo
[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

wget http://mirrors.aliyun.com/repo/Centos-7.repo -O /etc/yum.repos.d/CentOS-Base.repo
wget http://mirrors.aliyun.com/repo/epel-7.repo -O /etc/yum.repos.d/epel.repo 
wget https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo -O /etc/yum.repos.d/docker-ce.repo

2. 部署keepalived和haproxy

1) 安裝keepalived和haproxy

在node-01和node-02安裝keepalived和haproxy

yum install -y keepalived haproxy

2) 修改配置

keepalived配置

node-01的priority為100，node-02的priority為90，其他配置一樣。

[root@node-01 ~]# cat /etc/keepalived/keepalived.conf
! Configuration File for keepalived

global_defs {
   notification_email {
        [email protected]
   }
   notification_email_from [email protected]
   smtp_server 127.0.0.1
   smtp_connect_timeout 30
   router_id LVS_1
}

vrrp_instance VI_1 {
    state MASTER          
    interface eth0
    lvs_sync_daemon_inteface eth0
    virtual_router_id 88
    advert_int 1
    priority 100         
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    virtual_ipaddress {
      10.31.90.200/24
    }
}

haproxy配置

node-01和node-02的haproxy配置是一樣的。此處我們監聽的是10.31.90.200的8443端口，因為haproxy是和k8s apiserver是部署在同一臺服務器上，都用6443會沖突。

global
        chroot  /var/lib/haproxy
        daemon
        group haproxy
        user haproxy
        log 127.0.0.1:514 local0 warning
        pidfile /var/lib/haproxy.pid
        maxconn 20000
        spread-checks 3
        nbproc 8

defaults
        log     global
        mode    tcp
        retries 3
        option redispatch

listen https-apiserver
        bind 10.31.90.200:8443
        mode tcp
        balance roundrobin
        timeout server 15s
        timeout connect 15s

        server apiserver01 10.31.90.201:6443 check port 6443 inter 5000 fall 5
        server apiserver02 10.31.90.202:6443 check port 6443 inter 5000 fall 5
        server apiserver03 10.31.90.203:6443 check port 6443 inter 5000 fall 5

3) 啟動服務

systemctl enable keepalived && systemctl start keepalived 
systemctl enable haproxy && systemctl start haproxy

3. 部署kubernetes

1) 安裝軟件

由於kubeadm對Docker的版本是有要求的，需要安裝與kubeadm匹配的版本。
由於版本更新頻繁，請指定對應的版本號，本文采用1.13.2版本，其它版本未經測試。

yum install -y kubelet-1.13.1 kubeadm-1.13.1 kubectl-1.13.1 ipvsadm ipset docker-ce-18.06.1.ce

#啟動docker
systemctl enable docker && systemctl start docker

#設置kubelet開機自啟動
systemctl enable kubelet

2) 修改初始化配置

[root@node-01 ~]# cat kubeadm-init.yaml 
apiVersion: kubeadm.k8s.io/v1beta1
bootstrapTokens:
- groups:
  - system:bootstrappers:kubeadm:default-node-token
  token: abcdef.0123456789abcdef
  ttl: 24h0m0s
  usages:
  - signing
  - authentication
kind: InitConfiguration
localAPIEndpoint:
  advertiseAddress: 10.31.90.201
  bindPort: 6443
nodeRegistration:
  criSocket: /var/run/dockershim.sock
  name: node-01
  taints:
  - effect: NoSchedule
    key: node-role.kubernetes.io/master
---
apiVersion: kubeadm.k8s.io/v1beta1
kind: ClusterConfiguration
apiServer:
  timeoutForControlPlane: 4m0s
certificatesDir: /etc/kubernetes/pki
clusterName: kubernetes
controlPlaneEndpoint: "10.31.90.200:8443"
dns:
  type: CoreDNS
etcd:
  local:
    dataDir: /var/lib/etcd
imageRepository: registry.cn-hangzhou.aliyuncs.com/google_containers
kubernetesVersion: v1.13.2
networking:
  dnsDomain: cluster.local
  podSubnet: ""
  serviceSubnet: "10.245.0.0/16"
scheduler: {}
controllerManager: {}
---
apiVersion: kubeproxy.config.k8s.io/v1alpha1
kind: KubeProxyConfiguration
mode: "ipvs"

3) 預下載鏡像

[root@node-01 ~]# kubeadm config images pull --config kubeadm-init.yaml 
[config/images] Pulled registry.cn-hangzhou.aliyuncs.com/google_containers/kube-apiserver:v1.13.2
[config/images] Pulled registry.cn-hangzhou.aliyuncs.com/google_containers/kube-controller-manager:v1.13.2
[config/images] Pulled registry.cn-hangzhou.aliyuncs.com/google_containers/kube-scheduler:v1.13.2
[config/images] Pulled registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy:v1.13.2
[config/images] Pulled registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.1
[config/images] Pulled registry.cn-hangzhou.aliyuncs.com/google_containers/etcd:3.2.24
[config/images] Pulled registry.cn-hangzhou.aliyuncs.com/google_containers/coredns:1.2.6

4) 初始化

[root@node-01 ~]# kubeadm init --config kubeadm-init.yaml    
[init] Using Kubernetes version: v1.13.2
[preflight] Running pre-flight checks
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using ‘kubeadm config images pull‘
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Activating the kubelet service
[certs] Using certificateDir folder "/etc/kubernetes/pki"
[certs] Generating "ca" certificate and key
[certs] Generating "apiserver" certificate and key
[certs] apiserver serving cert is signed for DNS names [node-01 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.12.0.1 10.31.90.201 10.31.90.200]
[certs] Generating "apiserver-kubelet-client" certificate and key
[certs] Generating "etcd/ca" certificate and key
[certs] Generating "etcd/server" certificate and key
[certs] etcd/server serving cert is signed for DNS names [node-01 localhost] and IPs [10.31.90.201 127.0.0.1 ::1]
[certs] Generating "etcd/peer" certificate and key
[certs] etcd/peer serving cert is signed for DNS names [node-01 localhost] and IPs [10.31.90.201 127.0.0.1 ::1]
[certs] Generating "etcd/healthcheck-client" certificate and key
[certs] Generating "apiserver-etcd-client" certificate and key
[certs] Generating "front-proxy-ca" certificate and key
[certs] Generating "front-proxy-client" certificate and key
[certs] Generating "sa" key and public key
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[endpoint] WARNING: port specified in controlPlaneEndpoint overrides bindPort in the controlplane address
[kubeconfig] Writing "admin.conf" kubeconfig file
[endpoint] WARNING: port specified in controlPlaneEndpoint overrides bindPort in the controlplane address
[kubeconfig] Writing "kubelet.conf" kubeconfig file
[endpoint] WARNING: port specified in controlPlaneEndpoint overrides bindPort in the controlplane address
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
[endpoint] WARNING: port specified in controlPlaneEndpoint overrides bindPort in the controlplane address
[kubeconfig] Writing "scheduler.conf" kubeconfig file
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
[control-plane] Creating static Pod manifest for "kube-scheduler"
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[apiclient] All control plane components are healthy after 22.503955 seconds
[uploadconfig] storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace
[kubelet] Creating a ConfigMap "kubelet-config-1.13" in namespace kube-system with the configuration for the kubelets in the cluster
[patchnode] Uploading the CRI Socket information "/var/run/dockershim.sock" to the Node API object "node-01" as an annotation
[mark-control-plane] Marking the node node-01 as control-plane by adding the label "node-role.kubernetes.io/master=‘‘"
[mark-control-plane] Marking the node node-01 as control-plane by adding the taints [node-role.kubernetes.io/master:NoSchedule]
[bootstrap-token] Using token: abcdef.0123456789abcdef
[bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles
[bootstraptoken] configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials
[bootstraptoken] configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token
[bootstraptoken] configured RBAC rules to allow certificate rotation for all node client certificates in the cluster
[bootstraptoken] creating the "cluster-info" ConfigMap in the "kube-public" namespace
[addons] Applied essential addon: CoreDNS
[endpoint] WARNING: port specified in controlPlaneEndpoint overrides bindPort in the controlplane address
[addons] Applied essential addon: kube-proxy

Your Kubernetes master 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

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/

You can now join any number of machines by running the following on each node
as root:

  kubeadm join 10.31.90.200:8443 --token abcdef.0123456789abcdef --discovery-token-ca-cert-hash sha256:84201a329ec4388263e97303c6e4de50c2de2aa157a3b961cb8a6f325fadedb1

kubeadm init主要執行了以下操作：

  • [init]：指定版本進行初始化操作

  • [preflight] ：初始化前的檢查和下載所需要的Docker鏡像文件

  • [kubelet-start] ：生成kubelet的配置文件”/var/lib/kubelet/config.yaml”，沒有這個文件kubelet無法啟動，所以初始化之前的kubelet實際上啟動失敗。

  • [certificates]：生成Kubernetes使用的證書，存放在/etc/kubernetes/pki目錄中。

  • [kubeconfig] ：生成 KubeConfig 文件，存放在/etc/kubernetes目錄中，組件之間通信需要使用對應文件。

  • [control-plane]：使用/etc/kubernetes/manifest目錄下的YAML文件，安裝 Master 組件。

  • [etcd]：使用/etc/kubernetes/manifest/etcd.yaml安裝Etcd服務。

  • [wait-control-plane]：等待control-plan部署的Master組件啟動。

  • [apiclient]：檢查Master組件服務狀態。

  • [uploadconfig]：更新配置

  • [kubelet]：使用configMap配置kubelet。

  • [patchnode]：更新CNI信息到Node上，通過註釋的方式記錄。

  • [mark-control-plane]：為當前節點打標簽，打了角色Master，和不可調度標簽，這樣默認就不會使用Master節點來運行Pod。

  • [bootstrap-token]：生成token記錄下來，後邊使用kubeadm join往集群中添加節點時會用到

  • [addons]：安裝附加組件CoreDNS和kube-proxy

5) 為kubectl準備Kubeconfig文件

kubectl默認會在執行的用戶家目錄下面的.kube目錄下尋找config文件。這裏是將在初始化時[kubeconfig]步驟生成的admin.conf拷貝到.kube/config。

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

在該配置文件中，記錄了API Server的訪問地址，所以後面直接執行kubectl命令就可以正常連接到API Server中。

6) 查看組件狀態

[root@node-01 ~]# kubectl get cs
NAME                 STATUS    MESSAGE              ERROR
scheduler            Healthy   ok                   
controller-manager   Healthy   ok                   
etcd-0               Healthy   {"health": "true"}  
[root@node-01 ~]# kubectl get node
NAME      STATUS   ROLES    AGE   VERSION
node-01   NotReady    master   14m   v1.13.2

目前只有一個節點，角色是Master，狀態是NotReady。

7) 其他master部署

在node-01將證書文件拷貝至其他master節點

USER=root
CONTROL_PLANE_IPS="node-02 node-03"
for host in ${CONTROL_PLANE_IPS}; do
    ssh "${USER}"@$host "mkdir -p /etc/kubernetes/pki/etcd"
    scp /etc/kubernetes/pki/ca.* "${USER}"@$host:/etc/kubernetes/pki/
    scp /etc/kubernetes/pki/sa.* "${USER}"@$host:/etc/kubernetes/pki/
    scp /etc/kubernetes/pki/front-proxy-ca.* "${USER}"@$host:/etc/kubernetes/pki/
    scp /etc/kubernetes/pki/etcd/ca.* "${USER}"@$host:/etc/kubernetes/pki/etcd/
    scp /etc/kubernetes/admin.conf "${USER}"@$host:/etc/kubernetes/
done

在其他master執行,註意--experimental-control-plane參數

kubeadm join 10.31.90.200:8443 --token abcdef.0123456789abcdef --discovery-token-ca-cert-hash sha256:84201a329ec4388263e97303c6e4de50c2de2aa157a3b961cb8a6f325fadedb1 --experimental-control-plane

8) node部署

在node-04、node-05、node-06執行,註意沒有--experimental-control-plane參數

kubeadm join 10.31.90.200:8443 --token abcdef.0123456789abcdef --discovery-token-ca-cert-hash sha256:84201a329ec4388263e97303c6e4de50c2de2aa157a3b961cb8a6f325fadedb1

9) 部署網絡插件weave

Master節點NotReady的原因就是因為沒有使用任何的網絡插件，此時Node和Master的連接還不正常。目前最流行的Kubernetes網絡插件有Flannel、Calico、Canal、Weave這裏選擇使用Weave。

[root@node-01 ~]# kubectl apply -f "https://cloud.weave.works/k8s/net?k8s-version=$(kubectl version | base64 | tr -d ‘\n‘)"

10) 查看節點狀態

所有的節點已經處於Ready狀態。

[root@node-01 ~]# kubectl get node
NAME      STATUS   ROLES    AGE   VERSION
node-01   Ready    master   35m   v1.13.2
node-02   Ready    master   36m   v1.13.2
node-03   Ready    master   36m   v1.13.2
node-04   Ready    <none>   40m   v1.13.2
node-05   Ready    <none>   40m   v1.13.2
node-06   Ready    <none>   40m   v1.13.2

查看pod

[root@node-01 ~]# kubectl get pod -n kube-system
NAME                                        READY   STATUS    RESTARTS   AGE
coredns-89cc84847-j8mmg                     1/1     Running   0          1d
coredns-89cc84847-rbjxs                     1/1     Running   0          1d
etcd-node-01                                1/1     Running   1          1d
etcd-node-02                                1/1     Running   0          1d
etcd-node-03                                1/1     Running   0          1d
kube-apiserver-node-01                      1/1     Running   0          1d
kube-apiserver-node-02                      1/1     Running   0          1d
kube-apiserver-node-03                      1/1     Running   0          1d
kube-controller-manager-node-01             1/1     Running   2          1d
kube-controller-manager-node-02             1/1     Running   0          1d
kube-controller-manager-node-03             1/1     Running   0          1d
kube-proxy-jfbmv                            1/1     Running   0          1d
kube-proxy-lvkms                            1/1     Running   0          1d
kube-proxy-qx7kh                            1/1     Running   0          1d
kube-proxy-xst5v                            1/1     Running   0          1d
kube-proxy-zfwrk                            1/1     Running   0          1d
kube-proxy-ztg6j                            1/1     Running   0          1d
kube-scheduler-node-01                      1/1     Running   1          1d
kube-scheduler-node-02                      1/1     Running   1          1d
kube-scheduler-node-03                      1/1     Running   1          1d
weave-net-2xr7j                             2/2     Running   0          1d
weave-net-6x2gn                             2/2     Running   1          1d
weave-net-l6fdw                             2/2     Running   1          1d
weave-net-mswmj                             2/2     Running   2          1d
weave-net-skdw7                             2/2     Running   1          1d
weave-net-zm7zf                             2/2     Running   1          1d

查看ipvs的狀態

[root@node-01 ~]# ipvsadm -L -n
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
  -> RemoteAddress:Port           Forward Weight ActiveConn InActConn  
TCP  10.245.0.1:443 rr
  -> 10.31.90.201:6443            Masq    1      2          0         
  -> 10.31.90.202:6443            Masq    1      0          0         
  -> 10.31.90.203:6443            Masq    1      2          0         
TCP  10.245.0.10:53 rr
  -> 10.32.0.3:53                 Masq    1      0          0         
  -> 10.32.0.4:53                 Masq    1      0          0                
TCP  10.245.90.161:80 rr
  -> 10.45.0.1:80                 Masq    1      0          0         
TCP  10.245.90.161:443 rr
  -> 10.45.0.1:443                Masq    1      0          0         
TCP  10.245.149.227:1 rr
  -> 10.31.90.204:1               Masq    1      0          0         
  -> 10.31.90.205:1               Masq    1      0          0         
  -> 10.31.90.206:1               Masq    1      0          0         
TCP  10.245.181.126:80 rr
  -> 10.34.0.2:80                 Masq    1      0          0         
  -> 10.45.0.0:80                 Masq    1      0          0         
  -> 10.46.0.0:80                 Masq    1      0          0             
UDP  10.245.0.10:53 rr
  -> 10.32.0.3:53                 Masq    1      0          0         
  -> 10.32.0.4:53                 Masq    1      0          0

至此kubernetes集群部署完成。如有問題歡迎在下面留言交流。希望大家多多關註和點贊，謝謝！

kubeadm安裝kubernetes 1.13.2多master高可用集群

相關推薦

kubeadm安裝kubernetes 1.13.2多master高可用集群

nonlocal lap done mkdir -p cati waiting alived str token 1. 簡介 Kubernetes v1.13版本發布後，kubeadm才正式進入GA，可以生產使用,用kubeadm部署kubernetes集群也是以後的發展趨

centos7使用kubeadm安裝kubernetes 1.11版本多主高可用

ips refresh www ember issues abi dash iyu let centos7使用kubeadm安裝kubernetes 1.11版本多主高可用 [TOC] kubernetes介紹要學習一個新的東西，先了解它是什麽，熟悉基本概念會有很大幫助。以

centos7使用kubeadm安裝kubernetes 1.11版本多主高可用_Kubernetes中文社群

大佬，你好，照著這個方法搭建的成功後，卻無法使用heapster監控，部署後報錯heapster容器報錯 I0816 10:04:59.743015 1 heapster.go:72] /heapster –source=kubernetes:https://kubernetes.default

kubeadm 安裝 Kubernetes 1.6.2 過程中的一些坑_Kubernetes中文社群

因為一些莫可名狀的原因，國內網路使用 Kubeadm 頗有難度，這裡大概說一下過程中的一些坑。 1/4 準備工作 這裡用包管理的方式安裝 kubeadm、Docker 等元件。需要注意一點點的是，如果用的非 Root 使用者，要注意 sudo 的時候的環境代理設定問題。或者乾脆在 apt/y

kubeadm安裝kubernetes 1.13.1叢集完整部署記錄

k8s是什麼 　　Kubernetes簡稱為k8s，它是 Google 開源的容器叢集管理系統。在 Docker 技術的基礎上，為容器化的應用提供部署執行、資源排程、服務發現和動態伸縮等一系列完整功能，提高了大規模容器叢集管理的便捷性。k8s是容器到容器雲後的產物。但是k8s並不是萬能，並不一

使用Kubeadm搭建Kubernetes(1.12.2)叢集

Kubeadm是Kubernetes官方提供的用於快速安裝Kubernetes叢集的工具，伴隨Kubernetes每個版本的釋出都會同步更新，在2018年將進入GA狀態，說明離生產環境中使用的距離越來越近了。 使用Kubeadm搭建Kubernetes叢集本來是件很簡單的事，但由於眾所周知的原因，在中國大陸

轉 centos7使用kubeadm安裝kubernetes 1.12版本

最近在學習go 模板語法  還是有點小忙 !   感覺寫這種 kuberadm 搭建 kubernetes  還是有點水  好吧 可能我太高調了  前前後後搭過四 五次了  ！ kuber

使用kubeadm安裝Kubernetes 1.12_Kubernetes中文社群

kubeadm是Kubernetes官方提供的用於快速安裝Kubernetes叢集的工具，伴隨Kubernetes每個版本的釋出都會同步更新，kubeadm會對叢集配置方面的一些實踐做調整，通過實驗kubeadm可以學習到Kubernetes官方在叢集配置上一些新的最佳實踐。 在Kuberne

使用kubeadm安裝Kubernetes 1.8版本_Kubernetes中文社群

kubeadm是Kubernetes官方提供的快速安裝和初始化Kubernetes叢集的工具，目前的還處於孵化開發狀態，伴隨Kubernetes每個版本的釋出都會同步更新。 當然，目前的kubeadm是不能用於生產環境的。 但伴隨著Kubernetes每次版本升級，kubeadm都會對叢集配

利用 Kubeadm部署 Kubernetes 1.13.1 叢集實踐錄

概 述 Kubernetes叢集的搭建方法其實有多種，比如我在之前的文章《利用K8S技術棧打造個人私有云（連載之：K8S叢集搭建）》中使用的就是二進位制的安裝方法。雖然這種方法有利於我們理解 k8s叢集，但卻過於繁瑣。而 kubeadm是 Kubernetes官方提供的用於快速部署Kubernete

CentOS-7使用kubeadm安裝Kubernetes-1.12.0（how & why）

前言 安裝部署看似基礎，但其中蘊含許多值得深挖的原理。本篇文章不同於一般的部署文章的區別是，除了闡述基本的安裝部署過程，還詳細備註了每一步為何要如此配置，希望能讓讀者知其然更知其所以然。 1. 準備工作 1.1 環境資訊 作業系統：CentOS-7.5.1804

kubeadm部署kubernetes 1.13.1叢集

kubeadm是Kubernetes官方提供的用於快速部署Kubernetes叢集的工具，本次使用kubeadm搭建一個3節點的單叢集k8s。 #kubernetes部署dashboard視覺化外掛： https://blog.csdn.net/networken/articl

18.1集群介紹 18.2 keepalived介紹18.3/18.4/18.5 用keepalived配置高可用集群

18.1集群介紹 18.2 keepalived介紹18.3/18.4/18.5 用keepalived配置高可用集群- 18.1 集群介紹 - 18.2 keepalived介紹 - 18.3/18.4/18.5 用keepalived配置高可用集群 - 擴展 - heartbeat和keepalived

18.1 集群介紹 18.2 keepalived介紹 18.3/18.4/18.5 用keepalived配置高可用集群

18.1 集群介紹 18.2 keepalived介紹 18.3/18.4/18.5 用keepalived配置高可用集群- 18.6 負載均衡集群介紹 - 18.7 LVS介紹 - 18.8 LVS調度算法 - 18.9/18.10 LVS NAT模式搭建 - 擴展 - lvs 三種模式詳解 http:/

ActiveMQ 高可用集群安裝、配置（ZooKeeper + LevelDB）

訪問 wrap 創建 管理 apache link over love 其他 ActiveMQ 高可用集群安裝、配置（ZooKeeper + LevelDB） 1、ActiveMQ 集群部署規劃： 環境： JDK7 版本：ActiveMQ 5.11.1 ZooKeep

18.1集群介紹18.2keepalived介紹18.3-5用keepalived配置高可用集群

十五周四次課（4月9日）18.1集群介紹18.2 keepalived介紹18.3 18.4 18.5 用keepalived配置高可用集群這裏是用ngixn作為高可用的演示對象，因為有生產中很多企業用nginx作為負載均衡器使用編輯130上keepalived配置文件，內容從https://coding.n

postgresql高可用集群安裝

postgresql一、hosts and topology structure of pg cluster 1.host infos cluster01_node01 192.168.0.108cluster01_node02 192.168.0.109cluster02_node03 192.168.0.

Linux集群架構(1)集群介紹、keepalived介紹、用keepalived配置高可用集群

高可用keepalived 集群介紹 這些實現高可用和負載均衡的都是軟件，是為我們在服務器上的服務所作用的。 keepalived介紹 用keepalived配置高可用集群在nginx上實現高可用： 準備工作:準備兩臺機器133和

18.1-18.5 集群介紹，用keepalived配置高可用集群

高可用 keepalived 集群 18.1 集群介紹根據功能劃分為兩大類：高可用和負載均衡高可用集群通常為兩臺服務器，一臺工作，另外一臺作為冗余，當提供服務的機器宕機，冗余將接替繼續提供服務大概意思是：高可用一般使用兩臺機器，功能，角色是一樣的。當一臺服務器宕機不能服務了，利用另外的服務器頂替。

corosync+pacemaker配置高可用集群（需要額外安裝crm工具）

自用借鑒了網上不少博客定義：（來源於百度百科）Corosync：是集群管理套件的一部分，它在傳遞信息的時候可以通過一個簡單的配置文件來定義信息傳遞的方式和協議等。Pacemaker：是一個集群資源管理器。它利用集群基礎構件（OpenAIS 、heartbeat或corosync）提供的消息和成員管理能力來探測