centos7使用kubeadm配置高可用k8s集羣

時間 2019-12-05

標籤 centos7 centos 使用 kubeadm 配置可用 k8s 集羣欄目 Tomcat 简体版

原文原文鏈接

簡介

使用kubeadm配置多master節點，實現高可用。html

安裝

實驗環境說明

實驗架構圖

lab1: etcd master haproxy keepalived 11.11.11.111
lab2: etcd master haproxy keepalived 11.11.11.112
lab3: etcd master haproxy keepalived 11.11.11.113
lab4: node  11.11.11.114
lab5: node  11.11.11.115
lab6: node  11.11.11.116

vip(loadblancer ip): 11.11.11.110
複製代碼

實驗使用的`Vagrantfile`

# -*- mode: ruby -*-
# vi: set ft=ruby :

ENV["LC_ALL"] = "en_US.UTF-8"

Vagrant.configure("2") do |config|
    (1..6).each do |i|
      config.vm.define "lab#{i}" do |node|
        node.vm.box = "centos-7.4-docker-17"
        node.ssh.insert_key = false
        node.vm.hostname = "lab#{i}"
        node.vm.network "private_network", ip: "11.11.11.11#{i}"
        node.vm.provision "shell",
          inline: "echo hello from node #{i}"
        node.vm.provider "virtualbox" do |v|
          v.cpus = 2
          v.customize ["modifyvm", :id, "--name", "lab#{i}", "--memory", "2048"]
        end
      end
    end
end
複製代碼

在全部機器上安裝kubeadm

參考以前的文章《centos7安裝kubeadm》node

配置全部節點的kubelet

# 配置kubelet使用國內可用鏡像
# 修改/etc/systemd/system/kubelet.service.d/10-kubeadm.conf
# 添加以下配置 
Environment="KUBELET_EXTRA_ARGS=--pod-infra-container-image=registry.cn-shanghai.aliyuncs.com/gcr-k8s/pause-amd64:3.0"

# 使用命令
sed -i '/ExecStart=$/i Environment="KUBELET_EXTRA_ARGS=--pod-infra-container-image=registry.cn-shanghai.aliyuncs.com/gcr-k8s/pause-amd64:3.0"'  /etc/systemd/system/kubelet.service.d/10-kubeadm.conf

# 從新載入配置
systemctl daemon-reload
複製代碼

配置全部節點的hosts

cat >>/etc/hosts<<EOF
11.11.11.111 lab1
11.11.11.112 lab2
11.11.11.113 lab3
11.11.11.114 lab4
11.11.11.115 lab5
11.11.11.116 lab6
EOF
複製代碼

啓動etcd集羣

在lab1,lab2,lab3節點上啓動etcd集羣nginx

# lab1
docker stop etcd && docker rm etcd
rm -rf /data/etcd
mkdir -p /data/etcd
docker run -d \
--restart always \
-v /etc/etcd/ssl/certs:/etc/ssl/certs \
-v /data/etcd:/var/lib/etcd \
-p 2380:2380 \
-p 2379:2379 \
--name etcd \
registry.cn-hangzhou.aliyuncs.com/google_containers/etcd-amd64:3.1.12 \
etcd --name=etcd0 \
--advertise-client-urls=http://11.11.11.111:2379 \
--listen-client-urls=http://0.0.0.0:2379 \
--initial-advertise-peer-urls=http://11.11.11.111:2380 \
--listen-peer-urls=http://0.0.0.0:2380 \
--initial-cluster-token=9477af68bbee1b9ae037d6fd9e7efefd \
--initial-cluster=etcd0=http://11.11.11.111:2380,etcd1=http://11.11.11.112:2380,etcd2=http://11.11.11.113:2380 \
--initial-cluster-state=new \
--auto-tls \
--peer-auto-tls \
--data-dir=/var/lib/etcd

# lab2
docker stop etcd && docker rm etcd
rm -rf /data/etcd
mkdir -p /data/etcd
docker run -d \
--restart always \
-v /etc/etcd/ssl/certs:/etc/ssl/certs \
-v /data/etcd:/var/lib/etcd \
-p 2380:2380 \
-p 2379:2379 \
--name etcd \
registry.cn-hangzhou.aliyuncs.com/google_containers/etcd-amd64:3.1.12 \
etcd --name=etcd1 \
--advertise-client-urls=http://11.11.11.112:2379 \
--listen-client-urls=http://0.0.0.0:2379 \
--initial-advertise-peer-urls=http://11.11.11.112:2380 \
--listen-peer-urls=http://0.0.0.0:2380 \
--initial-cluster-token=9477af68bbee1b9ae037d6fd9e7efefd \
--initial-cluster=etcd0=http://11.11.11.111:2380,etcd1=http://11.11.11.112:2380,etcd2=http://11.11.11.113:2380 \
--initial-cluster-state=new \
--auto-tls \
--peer-auto-tls \
--data-dir=/var/lib/etcd

# lab3
docker stop etcd && docker rm etcd
rm -rf /data/etcd
mkdir -p /data/etcd
docker run -d \
--restart always \
-v /etc/etcd/ssl/certs:/etc/ssl/certs \
-v /data/etcd:/var/lib/etcd \
-p 2380:2380 \
-p 2379:2379 \
--name etcd \
registry.cn-hangzhou.aliyuncs.com/google_containers/etcd-amd64:3.1.12 \
etcd --name=etcd2 \
--advertise-client-urls=http://11.11.11.113:2379 \
--listen-client-urls=http://0.0.0.0:2379 \
--initial-advertise-peer-urls=http://11.11.11.113:2380 \
--listen-peer-urls=http://0.0.0.0:2380 \
--initial-cluster-token=9477af68bbee1b9ae037d6fd9e7efefd \
--initial-cluster=etcd0=http://11.11.11.111:2380,etcd1=http://11.11.11.112:2380,etcd2=http://11.11.11.113:2380 \
--initial-cluster-state=new \
--auto-tls \
--peer-auto-tls \
--data-dir=/var/lib/etcd

# 驗證查看集羣
docker exec -ti etcd ash
etcdctl member list
etcdctl cluster-health
exit
複製代碼

在第一臺master節點初始化

# 生成token
# 保留token後面還要使用
token=$(kubeadm token generate)
echo $token

# 生成配置文件
cat >kubeadm-master.config<<EOF
apiVersion: kubeadm.k8s.io/v1alpha1
kind: MasterConfiguration
kubernetesVersion: v1.10.1
#imageRepository: registry.cn-shanghai.aliyuncs.com/gcr-k8s
imageRepository: registry.cn-hangzhou.aliyuncs.com/google_containers

api:
  advertiseAddress: 11.11.11.111

apiServerExtraArgs:
  endpoint-reconciler-type: lease

controllerManagerExtraArgs:
  node-monitor-grace-period: 10s
  pod-eviction-timeout: 10s

networking:
  podSubnet: 192.168.0.0/16

etcd:
  endpoints:
  - "http://11.11.11.111:2379"
  - "http://11.11.11.112:2379"
  - "http://11.11.11.113:2379"

apiServerCertSANs:
- "lab1"
- "lab2"
- "lab3"
- "11.11.11.111"
- "11.11.11.112"
- "11.11.11.113"
- "11.11.11.110"
- "127.0.0.1"

token: $token
tokenTTL: "0"

featureGates:
  CoreDNS: true
EOF

# 初始化
kubeadm init --config kubeadm-master.config
systemctl enable kubelet

# 保存初始化完成以後的join命令
# 若是丟失可使用命令"kubeadm token list"獲取
# kubeadm join 11.11.11.111:6443 --token nevmjk.iuh214fc8i0k3iue --discovery-token-ca-cert-hash sha256:0e4f738348be836ff810bce754e059054845f44f01619a37b817eba83282d80f

# 配置kubectl使用
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config


# 安裝網絡插件
# 下載配置
mkdir flannel && cd flannel
wget https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml

# 修改配置
# 此處的ip配置要與上面kubeadm的pod-network一致
  net-conf.json: |
    {
      "Network": "192.168.0.0/16",
      "Backend": {
        "Type": "vxlan"
      }
    }

# 修改鏡像
image: registry.cn-shanghai.aliyuncs.com/gcr-k8s/flannel:v0.10.0-amd64

# 啓動
kubectl apply -f kube-flannel.yml

# 若是Node有多個網卡的話，參考flannel issues 39701，
# https://github.com/kubernetes/kubernetes/issues/39701
# 目前須要在kube-flannel.yml中使用--iface參數指定集羣主機內網網卡的名稱，
# 不然可能會出現dns沒法解析。容器沒法通訊的狀況，須要將kube-flannel.yml下載到本地，
# flanneld啓動參數加上--iface=<iface-name>
    containers:
      - name: kube-flannel
        image: registry.cn-shanghai.aliyuncs.com/gcr-k8s/flannel:v0.10.0-amd64
        command:
        - /opt/bin/flanneld
        args:
        - --ip-masq
        - --kube-subnet-mgr
        - --iface=eth1

# 查看
kubectl get pods --namespace kube-system
kubectl get svc --namespace kube-system

# 設置master容許部署應用pod，參與工做負載，如今能夠部署其餘系統組件
# 如 dashboard, heapster, efk等
kubectl taint nodes --all node-role.kubernetes.io/master-
複製代碼

啓動其餘master節點

# 打包第一臺master初始化以後的/etc/kubernetes/pki目錄
cd /etc/kubernetes && tar czvf /root/pki.tgz pki/ && cd ~

# 上傳到其餘master的/etc/kubernetes目錄下
tar xf pki.tgz -C /etc/kubernetes/

# 刪除pki目錄下的apiserver.crt 和 apiserver.key文件
rm -rf /etc/kubernetes/pki/{apiserver.crt,apiserver.key}

# 生成配置文件
# 使用和以前master同樣的配置文件
# token保持一致
cat >kubeadm-master.config<<EOF
apiVersion: kubeadm.k8s.io/v1alpha1
kind: MasterConfiguration
kubernetesVersion: v1.10.1
#imageRepository: registry.cn-shanghai.aliyuncs.com/gcr-k8s
imageRepository: registry.cn-hangzhou.aliyuncs.com/google_containers

# 注意修改IP
api:
  advertiseAddress: 11.11.11.112

apiServerExtraArgs:
  endpoint-reconciler-type: lease

controllerManagerExtraArgs:
  node-monitor-grace-period: 10s
  pod-eviction-timeout: 10s

networking:
  podSubnet: 192.168.0.0/16

etcd:
  endpoints:
  - "http://11.11.11.111:2379"
  - "http://11.11.11.112:2379"
  - "http://11.11.11.113:2379"

apiServerCertSANs:
- lab1
- lab2
- lab3
- "11.11.11.111"
- "11.11.11.112"
- "11.11.11.113"
- "11.11.11.110"
- "127.0.0.1"

token: nevmjk.iuh214fc8i0k3iue
tokenTTL: "0"

featureGates:
  CoreDNS: true
EOF

# 初始化
kubeadm init --config kubeadm-master.config
systemctl enable kubelet

# 查看狀態
kubectl get pod --all-namespaces -o wide | grep lab1
kubectl get pod --all-namespaces -o wide | grep lab2
kubectl get pod --all-namespaces -o wide | grep lab3
kubectl get nodes -o wide
複製代碼

配置haproxy代理和keepalived

在lab1,lab2,lab3節點上啓動haproxy和keepalivedgit

# 拉取haproxy鏡像
docker pull haproxy:1.7.8-alpine
mkdir /etc/haproxy
cat >/etc/haproxy/haproxy.cfg<<EOF
global
  log 127.0.0.1 local0 err
  maxconn 50000
  uid 99
  gid 99
  #daemon
  nbproc 1
  pidfile haproxy.pid

defaults
  mode http
  log 127.0.0.1 local0 err
  maxconn 50000
  retries 3
  timeout connect 5s
  timeout client 30s
  timeout server 30s
  timeout check 2s

listen admin_stats
  mode http
  bind 0.0.0.0:1080
  log 127.0.0.1 local0 err
  stats refresh 30s
  stats uri     /haproxy-status
  stats realm   Haproxy\ Statistics
  stats auth    will:will
  stats hide-version
  stats admin if TRUE

frontend k8s-https
  bind 0.0.0.0:8443
  mode tcp
  #maxconn 50000
  default_backend k8s-https

backend k8s-https
  mode tcp
  balance roundrobin
  server lab1 11.11.11.111:6443 weight 1 maxconn 1000 check inter 2000 rise 2 fall 3
  server lab2 11.11.11.112:6443 weight 1 maxconn 1000 check inter 2000 rise 2 fall 3
  server lab3 11.11.11.113:6443 weight 1 maxconn 1000 check inter 2000 rise 2 fall 3
EOF

# 啓動haproxy
docker run -d --name my-haproxy \
-v /etc/haproxy:/usr/local/etc/haproxy:ro \
-p 8443:8443 \
-p 1080:1080 \
--restart always \
haproxy:1.7.8-alpine

# 查看日誌
docker logs my-haproxy

# 瀏覽器查看狀態
http://11.11.11.111:1080/haproxy-status
http://11.11.11.112:1080/haproxy-status

# 拉取keepalived鏡像
docker pull osixia/keepalived:1.4.4

# 啓動
# 載入內核相關模塊
lsmod | grep ip_vs
modprobe ip_vs

# 啓動keepalived
# eth1爲本次實驗11.11.11.0/24網段的所在網卡
docker run --net=host --cap-add=NET_ADMIN \
-e KEEPALIVED_INTERFACE=eth1 \
-e KEEPALIVED_VIRTUAL_IPS="#PYTHON2BASH:['11.11.11.110']" \
-e KEEPALIVED_UNICAST_PEERS="#PYTHON2BASH:['11.11.11.111','11.11.11.112','11.11.11.113']" \
-e KEEPALIVED_PASSWORD=hello \
--name k8s-keepalived \
--restart always \
-d osixia/keepalived:1.4.4

# 查看日誌
# 會看到兩個成爲backup 一個成爲master
docker logs k8s-keepalived

# 此時會配置 11.11.11.110 到其中一臺機器
# ping測試
ping -c4 11.11.11.110

# 若是失敗後清理後，從新實驗
docker rm -f k8s-keepalived
ip a del 11.11.11.110/32 dev eth1

# 修改~/.kube/config文件裏ip和端口，而後使用kubectl測試
rm -rf .kube/cache .kube/http-cache
kubectl get pods -n kube-system -o wide
複製代碼

修改master節點相關組件配置指向vip

# lab1 lab2 lab3
sed -i 's@server: https://11.11.11.*:6443@server: https://11.11.11.110:8443@g' /etc/kubernetes/{admin.conf,kubelet.conf,scheduler.conf,controller-manager.conf}

# 重啓kubelet
systemctl daemon-reload
systemctl restart kubelet docker

# 查看全部節點狀態
kubectl get nodes -o wide
複製代碼

修改kube-proxy的配置

# 修改kube-proxy的配置指定vip
# 執行命令以後修改成 server: https://11.11.11.110:8443
kubectl edit -n kube-system configmap/kube-proxy

# 查看設置
kubectl get -n kube-system configmap/kube-proxy -o yaml

# 刪除重建kube-proxy
kubectl get pods --all-namespaces -o wide | grep proxy
all_proxy_pods=$(kubectl get pods --all-namespaces -o wide | grep proxy | awk '{print $2}' | xargs)
echo $all_proxy_pods
kubectl delete pods $all_proxy_pods -n kube-system
kubectl get pods --all-namespaces -o wide | grep proxy
複製代碼

啓動node節點

# 加入master節點
# 這個命令是以前初始化master完成時，輸出的命令
kubeadm join 11.11.11.110:8443 --token nevmjk.iuh214fc8i0k3iue --discovery-token-ca-cert-hash sha256:0e4f738348be836ff810bce754e059054845f44f01619a37b817eba83282d80f
systemctl enable kubelet
複製代碼

修改node節點kubelet配置並重啓

# 修改配置
sed -i 's@server: https://11.11.11.*:6443@server: https://11.11.11.110:8443@g' /etc/kubernetes/kubelet.conf

# 重啓kubelet
systemctl daemon-reload
systemctl restart kubelet docker

# 查看全部節點狀態
kubectl get nodes -o wide
複製代碼

禁止master節點發布應用github

設置master不接受負載docker

# 查看狀態
kubectl get nodes

# 設置
# kubectl patch node lab1 -p '{"spec":{"unschedulable":true}}'
kubectl taint nodes lab1 lab2 lab3 node-role.kubernetes.io/master=true:NoSchedule

# 查看狀態
kubectl get nodes
複製代碼

測試

重建多個coredns副本

# 刪除coredns的pods
kubectl get pods -n kube-system -o wide | grep coredns
all_coredns_pods=$(kubectl get pods -n kube-system -o wide | grep coredns | awk '{print $1}' | xargs)
echo $all_coredns_pods
kubectl delete pods $all_coredns_pods -n kube-system

# 修改副本數
# replicas: 3
# 能夠修改成node節點的個數
kubectl edit deploy coredns -n kube-system

# 查看狀態
kubectl get pods -n kube-system -o wide | grep coredns
複製代碼

基礎測試

1. 啓動shell

# 直接使用命令測試
kubectl run nginx --replicas=2 --image=nginx:alpine --port=80
kubectl expose deployment nginx --type=NodePort --name=example-service-nodeport
kubectl expose deployment nginx --name=example-service

# 使用配置文件測試
cat >example-nginx.yml<<EOF
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: nginx
spec:
  replicas: 2
  template:
    metadata:
      labels:
        app: nginx
    spec:
      restartPolicy: Always
      containers:
      - name: nginx
        image: nginx:alpine
        ports:
        - containerPort: 80
        livenessProbe:
          httpGet:
            path: /
            port: 80
          initialDelaySeconds: 10
          periodSeconds: 3
        readinessProbe:
          httpGet:
            path: /
            port: 80
          initialDelaySeconds: 10
          periodSeconds: 3
---
kind: Service
apiVersion: v1
metadata:
  name: example-service
spec:
    selector:
      app: nginx
    ports:
      - name: http
        port: 80
        targetPort: 80

---
kind: Service
apiVersion: v1
metadata:
  name: example-service-nodeport
spec:
    selector:
      app: nginx
    type: NodePort
    ports:
      - name: http-nodeport
        port: 80
        nodePort: 32223
EOF
kubectl apply -f example-nginx.yml
複製代碼

2. 查看狀態json

kubectl get deploy
kubectl get pods
kubectl get svc
kubectl describe svc example-service
複製代碼

3. DNS解析centos

kubectl run curl --image=radial/busyboxplus:curl -i --tty
nslookup kubernetes
nslookup example-service
curl example-service

# 若是時間過長會返回錯誤，可使用以下方式再進入測試
curlPod=$(kubectl get pod | grep curl | awk '{print $1}')
kubectl exec -ti $curlPod -- sh
複製代碼

4. 訪問測試api

# 10.96.59.56 爲查看svc時獲取到的clusterip
curl "10.96.59.56:80"

# 32223 爲查看svc時獲取到的 nodeport
http://11.11.11.114:32223/
http://11.11.11.115:32223/
複製代碼

3. 清理刪除

kubectl delete svc example-service example-service-nodeport
kubectl delete deploy nginx curl
複製代碼

高可用測試

關閉master節點測試集羣是可否正常執行上一步的基礎測試，查看相關信息，不能同時關閉lab1和lab2，由於上面有haproxy和keepalived服務

kubectl get pod --all-namespaces -o wide
kubectl get pod --all-namespaces -o wide | grep lab1
kubectl get pod --all-namespaces -o wide | grep lab2
kubectl get pod --all-namespaces -o wide | grep lab3
kubectl get nodes -o wide
kubectl get deploy
kubectl get pods
kubectl get svc
kubectl describe svc example-service
複製代碼

注意事項

當直接把node節點關閉時，只有過了5分鐘以後，上面的pod纔會被檢測到有問題，並遷移到其餘節點

若是想快速遷移能夠執行 kubectl delete node

也能夠修改controller-manager的的pod-eviction-timeout參數，默認5m

node-monitor-grace-period參數，默認40s

參考文檔

https://kubernetes.io/docs/admin/high-availability/
https://www.kubernetes.org.cn/3536.html
https://github.com/indiketa/kubeadm-ha
https://zhuanlan.zhihu.com/p/34740013
https://github.com/cookeem/kubeadm-ha/blob/master/README_CN.md
https://blog.frognew.com/2017/04/install-etcd-cluster.html
https://blog.frognew.com/2017/04/install-ha-kubernetes-1.6-cluster.html
https://medium.com/@bambash/ha-kubernetes-cluster-via-kubeadm-b2133360b198
https://github.com/kubernetes/kubeadm/issues/546
https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-init/#config-file