前言
本實驗建立在Kubernetes單節點二進制部署基礎之上，

實驗環境

k8s集群master01:192.168.19.11  kube-apiserver kube-controller-manager kube-scheduler etcd
k8s集群master02:192.168.19.33 （為多節點準備）

k8s集群node01:192.168.19.44   kubelet kube-proxy docker flannel
k8s集群node02: 192.168.19.55

etcd集群節點1:192.168.19.11   etcd
etcd集群節點2:192.168.19.44
etcd集群節點3:192.168.19.55

負載均衡nginx+keepalive01 (master）:192.168.19.66
負載均衡nginx+keepalive02 (backup）:192.168.19.77

systemetl stop firewalld
systemctl disable firewalldsetenforce 0

一、部署master02 節點

修改主機名，關閉防火墻

# k8smaster02（192.168.19.33）
hostnamectl set-hostname k8smaster02
su
systemctl stop firewalld.service
systemctl disable firewalld.service
setenforce 0

# lb01（192.168.19.66）
hostnamectl set-hostname lb01
su
systemctl stop firewalld.service
systemctl disable firewalld.service
setenforce 0

# lb02（192.168.19.77）
hostnamectl set-hostname lb02
su
systemctl stop firewalld.service
systemctl disable firewalld.service
setenforce 0

在k8smaster01上操作

#從 k8smaster01 節點上拷貝證書檔案、各master組件的組態檔和服務管理檔案到 k8smaster02 節點
scp -r /opt/etcd/ root@192.168.19.33:/opt/
scp -r /opt/kubernetes/ root@192.168.19.33:/opt
scp /usr/lib/systemd/system/{kube-apiserver,kube-controller-manager,kube-scheduler}.service root@192.168.19.33:/usr/lib/systemd/system/

在k8smaster02上操作

#修改組態檔kube-apiserver中的IP
vim /opt/kubernetes/cfg/kube-apiserver
KUBE_APISERVER_OPTS="--logtostderr=true \
--v=4 \
--etcd-servers=https://192.168.19.11:2379,https://192.168.19.44:2379,https://192.168.19.55:2379 \
--bind-address=192.168.19.33 \				#修改
--secure-port=6443 \
--advertise-address=192.168.19.33 \			#修改
......

#在 master02 節點上啟動各服務并設定開機自啟
systemctl start kube-apiserver.service
systemctl enable kube-apiserver.service
systemctl start kube-controller-manager.service
systemctl enable kube-controller-manager.service
systemctl start kube-scheduler.service
systemctl enable kube-scheduler.service

#查看node節點狀態
ln -s /opt/kubernetes/bin/* /usr/local/bin/
kubectl get nodes
kubectl get nodes -o wide			#-o=wide：輸出額外資訊；對于Pod，將輸出Pod所在的Node名

#此時在master02節點查到的node節點狀態僅是從etcd查詢到的資訊，而此時node節點實際上并未與master02節點建立通信連接，因此需要使用一個VIP把node節點與master節點都關聯起來

二、部署負載均衡

配置load balancer集群雙機熱備負載均衡（nginx實作負載均衡，keepalived實作雙機熱備）

1.配置nginx的官方在線yum源，配置本地nginx的yum源

在lb01、lb02節點上操作

#配置nginx的官方在線yum源，配置本地nginx的yum源
cat > /etc/yum.repos.d/nginx.repo << 'EOF'
[nginx]
name=nginx repo
baseurl=http://nginx.org/packages/centos/7/$basearch/
gpgcheck=0
EOF

yum install -y nginx 

#修改nginx組態檔，配置四層反向代理負載均衡，指定k8s群集2臺master的節點ip和6443埠
vim /etc/nginx/nginx.conf
events {
    worker_connections  1024;
}

#添加
stream {
    log_format  main  '$remote_addr $upstream_addr - [$time_local] $status $upstream_bytes_sent';
    
	access_log  /var/log/nginx/k8s-access.log  main;

    upstream k8s-apiserver {
        server 192.168.19.11:6443;
        server 192.168.19.33:6443;
    }
    server {
        listen 6443;
        proxy_pass k8s-apiserver;
    }
}

http {
......


#檢查組態檔語法
nginx -t   

#啟動nginx服務，查看已監聽6443埠
systemctl start nginx
systemctl enable nginx
netstat -natp | grep nginx

2.部署keepalived服務

在lb01、lb02節點上操作

yum install keepalived -y

#修改keepalived組態檔
vim /etc/keepalived/keepalived.conf
! Configuration File for keepalived

global_defs {
   # 接收郵件地址
   notification_email {
     acassen@firewall.loc
     failover@firewall.loc
     sysadmin@firewall.loc
   }
   # 郵件發送地址
   notification_email_from Alexandre.Cassen@firewall.loc
   smtp_server 127.0.0.1
   smtp_connect_timeout 30
   router_id NGINX_MASTER	#lb01節點的為 NGINX_MASTER，lb02節點的為 NGINX_BACKUP
}

#添加一個周期性執行的腳本
vrrp_script check_nginx {
    script "/etc/nginx/check_nginx.sh"	#指定檢查nginx存活的腳本路徑
}

vrrp_instance VI_1 {
    state MASTER			#lb01節點的為 MASTER，lb02節點的為 BACKUP
    interface ens33			#指定網卡名稱 ens33
    virtual_router_id 51	#指定vrid，兩個節點要一致
    priority 100			#lb01節點的為 100，lb02節點的為 90
    advert_int 1
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    virtual_ipaddress {
        192.168.19.100/24	#指定 VIP
    }
    track_script {
        check_nginx			#指定vrrp_script配置的腳本
    }
}

#創建nginx狀態檢查腳本 
vim /etc/nginx/check_nginx.sh
#!/bin/bash
#egrep -cv "grep|$$" 用于過濾掉包含grep 或者 $$ 表示的當前Shell行程ID
count=$(ps -ef | grep nginx | egrep -cv "grep|$$")

if [ "$count" -eq 0 ];then
    systemctl stop keepalived
fi


chmod +x /etc/nginx/check_nginx.sh

#啟動keepalived服務（一定要先啟動了nginx服務，再啟動keepalived服務）
systemctl start keepalived
systemctl enable keepalived
ip a				#查看VIP是否生成

3.修改k8snode節點上的bootstrap.kubeconfig,kubelet.kubeconfig組態檔為VIP

在node01和node02上操作

cd /opt/kubernetes/cfg/
ls
vim bootstrap.kubeconfig 
server: https://192.168.19.100:6443
                      
vim kubelet.kubeconfig
server: https://192.168.19.100:6443
                        
vim kube-proxy.kubeconfig
server: https://192.168.19.100:6443

#重啟kubelet和kube-proxy服務
systemctl restart kubelet.service 
systemctl restart kube-proxy.service

4.在lb01上查看nginx的k8s日志

tail /var/log/nginx/k8s-access.log

三、測驗

在 k8smaster01 節點上操作

#測驗創建pod
kubectl run nginx --image=nginx

#查看Pod的狀態資訊
kubectl get pods
NAME                    READY   STATUS    RESTARTS   AGE
nginx-dbddb74b8-5n654   1/1     Running   0          41s

kubectl get pods -o wide
NAME                    READY   STATUS    RESTARTS   AGE   IP            NODE            NOMINATED NODE
nginx-dbddb74b8-5n654   1/1     Running   0          71s   172.17.52.3   192.168.19.44   <none>
#READY為1/1，表示這個Pod中有1個容器

#在對應網段的node節點上操作，可以直接使用瀏覽器或者curl命令訪問
curl 172.17.52.3

#這時在master01節點上查看nginx日志，發現沒有權限查看
kubectl logs nginx-dbddb74b8-5n654


#在master01節點上，將cluster-admin角色授予用戶system:anonymous
kubectl create clusterrolebinding cluster-system-anonymous --clusterrole=cluster-admin --user=system:anonymous

#再次查看nginx日志
kubectl logs nginx-dbddb74b8-5n654