繼續前一章的部署。

部署 kube-proxy 組件

14.1 下載和分發二進制文件，參考 第三章

分發到各節點

source /opt/k8s/bin/environment.sh
for node_name in ${NODE_NAMES[@]}
  do
    echo ">>> ${node_name}"
    scp k8s/v1.11.2/server/kubernetes/server/bin/{kube-proxy,kubelet} k8s@${node_name}:/opt/k8s/bin/
    ssh k8s@${node_name} "chmod 755 /opt/k8s/bin/{kube-proxy,kubelet}
 
"
done

14.2 安裝依賴包，參考 第十一章

14.3 創建 kube-proxy 證書

cd /opt/k8s/cert

cat > kube-proxy-csr.json <<EOF
{
  "CN": "system:kube-proxy",
  "key": {
    "algo": "rsa",
    "size": 2048
  },
  "names": [
    {
      "C": "CN",
      "ST": "BeiJing",
      "L": "BeiJing",
      "O": "k8s",
      "OU": "4Paradigm
 
"
    }
  ]
}
EOF

• CN：指定該證書的 User 為 system:kube-proxy；
• 預定義的 RoleBinding system:node-proxier 將User system:kube-proxy 與 Role system:node-proxier 綁定，該 Role 授予了調用 kube-apiserver Proxy 相關 API 的權限；
• 該證書只會被 kube-proxy 當做 client 證書使用，所以 hosts 字段為空；

生成證書和私鑰:

cfssl gencert -ca=/etc/kubernetes/cert/ca.pem   -ca-key=/etc/kubernetes/cert/ca-key.pem   
 
-config=/etc/kubernetes/cert/ca-config.json   -profile=kubernetes  kube-proxy-csr.json | cfssljson -bare kube-proxy

創建和分發 kubeconfig 文件

source /opt/k8s/bin/environment.sh
kubectl config set-cluster kubernetes   --certificate-authority=/etc/kubernetes/cert/ca.pem   --embed-certs=true   --server=${KUBE_APISERVER}   --kubeconfig=kube-proxy.kubeconfig

kubectl config set-credentials kube-proxy   --client-certificate=kube-proxy.pem   --client-key=kube-proxy-key.pem   --embed-certs=true   --kubeconfig=kube-proxy.kubeconfig

kubectl config set-context default   --cluster=kubernetes   --user=kube-proxy   --kubeconfig=kube-proxy.kubeconfig

kubectl config use-context default --kubeconfig=kube-proxy.kubeconfig

• --embed-certs-true 將 ca.pem和admin.pem 證書內容嵌入到生成的 kubectl-proxy.kubeconfig 文件中（不加時，寫入的是證書文件的路徑）

分發 kubeconfig 文件

source /opt/k8s/bin/environment.sh
for node_name in ${NODE_NAMES[@]}
  do
    echo ">>> ${node_name}"
    scp kube-proxy.kubeconfig k8s@${node_name}:/etc/kubernetes/
done

14.3 創建 kube-proxy 配置文件

從 v1.10開始，kube-proxy 部分參數可以在配置文件中配置，可以使用 --write-config-to 選項生成該配置文件，或者參考 kubeproxyconfig 的類型定義源文件：

https://github.com/kubernetes/kubernetes/blob/master/pkg/proxy/apis/kubeproxyconfig/types.go

創建 kube-proxy config 文件模板：

cat >kube-proxy.config.yaml.template <<EOF
apiVersion: kubeproxy.config.k8s.io/v1alpha1
bindAddress: ##NODE_IP##
clientConnection:
  kubeconfig: /etc/kubernetes/kube-proxy.kubeconfig
clusterCIDR: ${CLUSTER_CIDR}
healthzBindAddress: ##NODE_IP##:10256
hostnameOverride: ##NODE_NAME##
kind: KubeProxyConfiguration
metricsBindAddress: ##NODE_IP##:10249
mode: "ipvs"
EOF

• bindAddress 監聽地址
• clientConnect.kubeconfig 連接 apiserver 的 kubeconfig 文件
• clusterCIDR kube-proxy 根據 --cluster-cidr 判斷集群內部和外部流量，指定 --cluster-cidr 或 --masquerade-all 選項後 kube-proxy 才會對訪問 Service IP 的請求做 SNAT
• hostnameOverride 參數值必須與 kubelet 的值一致，否則 kube-proxy 啟動後會找不到該 Node ，從而不會創建任何 ipvs 規則
• mode 使用 ipvs 模式

為各節點創建和分發 kube-proxy 配置文件

source /opt/k8s/bin/environment.sh
for (( i=0; i < 4; i++ ))
  do 
    echo ">>> ${NODE_NAMES[i]}"
    sed -e "s/##NODE_NAME##/${NODE_NAMES[i]}/" -e "s/##NODE_IP##/${NODE_IPS[i]}/" kube-proxy.config.yaml.template > kube-proxy-${NODE_NAMES[i]}.config.yaml
    scp kube-proxy-${NODE_NAMES[i]}.config.yaml root@${NODE_NAMES[i]}:/etc/kubernetes/kube-proxy.config.yaml
done

替換後的 kube-proxy.config.yaml如下

[root@k8s-n2 kubernetes]# cat /etc/kubernetes/kube-proxy.config.yaml
apiVersion: kubeproxy.config.k8s.io/v1alpha1
bindAddress: 192.168.56.31
clientConnection:
  kubeconfig: /etc/kubernetes/kube-proxy.kubeconfig
clusterCIDR: 172.30.0.0/16
healthzBindAddress: 192.168.56.31:10256
hostnameOverride: k8s-n2
kind: KubeProxyConfiguration
metricsBindAddress: 192.168.56.31:10249
mode: "ipvs"

14.4 創建和分發 kube-proxy systemd unit 文件

source /opt/k8s/bin/environment.sh
cat > kube-proxy.service <<EOF
[Unit]
Description=Kubernetes Kube-Proxy Server
Documentation=https://github.com/GoogleCloudPlatform/kubernetes
After=network.target

[Service]
WorkingDirectory=/var/lib/kube-proxy
ExecStart=/opt/k8s/bin/kube-proxy \  --config=/etc/kubernetes/kube-proxy.config.yaml \  --alsologtostderr=true \  --logtostderr=false \  --log-dir=/var/log/kubernetes \  --v=2
Restart=on-failure
RestartSec=5
LimitNOFILE=65536

[Install]
WantedBy=multi-user.target
EOF

分發 kube-proxy systemd unit 文件

source /opt/k8s/bin/environment.sh
for node_name in ${NODE_NAMES[@]}
  do 
    echo ">>> ${node_name}"
    scp kube-proxy.service root@${node_name}:/etc/systemd/system/
done

14.5 啟動 kube-proxy 服務

source /opt/k8s/bin/environment.sh
for node_ip in ${NODE_IPS[@]}
  do
    echo ">>> ${node_ip}"
    ssh root@${node_ip} "mkdir -p /var/lib/kube-proxy"
    ssh root@${node_ip} "mkdir -p /var/log/kubernetes && chown -R k8s /var/log/kubernetes"
    ssh root@${node_ip} "systemctl daemon-reload && systemctl enable kube-proxy && systemctl restart kube-proxy"
done

檢查啟動結果：

source /opt/k8s/bin/environment.sh
for node_ip in ${NODE_IPS[@]}
  do
    echo ">>> ${node_ip}"
    ssh k8s@${node_ip} "systemctl status kube-proxy|grep Active"
done

• 確保服務是 Active: active (running) 狀態
• 查看日誌: journalctl -u kube-proxy

查看監聽端口和 metrics

[k8s@k8s-m1 template]$ sudo netstat -lnpt|grep kube-prox
tcp        0      0 192.168.56.20:10249     0.0.0.0:*               LISTEN      729/kube-proxy      
tcp        0      0 192.168.56.20:10256     0.0.0.0:*               LISTEN      729/kube-proxy 

• 10249：http prometheus metrics port;
• 10256：http healthz port;

查看 ipvs 路由規則

[k8s@k8s-m1 template]$ source /opt/k8s/bin/environment.sh
[k8s@k8s-m1 template]$ for node_ip in ${NODE_IPS[@]}
>   do
>     echo ">>> ${node_ip}"
>     ssh root@${node_ip} "/usr/sbin/ipvsadm -ln"
>   done
>>> 192.168.56.20
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
  -> RemoteAddress:Port           Forward Weight ActiveConn InActConn
TCP  10.254.0.1:443 rr
  -> 192.168.56.20:6443           Masq    1      0          0         
  -> 192.168.56.21:6443           Masq    1      0          0         
>>> 192.168.56.21
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
  -> RemoteAddress:Port           Forward Weight ActiveConn InActConn
TCP  10.254.0.1:443 rr
  -> 192.168.56.20:6443           Masq    1      0          0         
  -> 192.168.56.21:6443           Masq    1      0          0         
>>> 192.168.56.30
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
  -> RemoteAddress:Port           Forward Weight ActiveConn InActConn
TCP  10.254.0.1:443 rr
  -> 192.168.56.20:6443           Masq    1      0          0         
  -> 192.168.56.21:6443           Masq    1      0          0         
>>> 192.168.56.31
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
  -> RemoteAddress:Port           Forward Weight ActiveConn InActConn
TCP  10.254.0.1:443 rr
  -> 192.168.56.20:6443           Masq    1      0          0         
  -> 192.168.56.21:6443           Masq    1      0          0    

可以看到，將所有到 kubernetes cluster ip 443 端口的請求都轉發到了 kube-apiserver 的 6443 端口

二進制安裝kubernetes v1.11.2 （第十四章 kube-proxy部署）