部署方式:
方式1. minikube
Minikube是一個(gè)工具,可以在本地快速運(yùn)行一個(gè)單點(diǎn)的Kubernetes,嘗試Kubernetes或日常開(kāi)發(fā)的用戶使用。不能用于生產(chǎn)環(huán)境。
官方地址:https://kubernetes.io/docs/setup/minikube/
方式2. kubeadm
Kubeadm也是一個(gè)工具,提供kubeadm init和kubeadm join,用于快速部署Kubernetes集群。
官方地址:https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm/
方式3. 直接使用epel-release yum源,缺點(diǎn)就是版本較低
方式4. 二進(jìn)制包
從官方下載發(fā)行版的二進(jìn)制包,手動(dòng)部署每個(gè)組件,組成Kubernetes集群。
官方也提供了一個(gè)互動(dòng)測(cè)試環(huán)境供大家測(cè)試:https://kubernetes.io/zh/docs/tutorials/kubernetes-basics/cluster-interactive/
https://kubernetes.io/docs/tutorials/kubernetes-basics/
二進(jìn)制方式部署 kubernetes 集群
目標(biāo)任務(wù)
1 Kubernetes集群部署架構(gòu)規(guī)劃
2 部署Etcd集群
3 在Node節(jié)點(diǎn)安裝Docker
4 部署Flannel網(wǎng)絡(luò)
5 在Master節(jié)點(diǎn)部署組件
6 在Node節(jié)點(diǎn)部署組件
7 查看集群狀態(tài)
8 運(yùn)行一個(gè)測(cè)試示例
9 部署Dashboard(Web UI)
1. 準(zhǔn)備
三臺(tái)虛擬機(jī)
固定IP、改名字、相互解析、關(guān)閉防火墻
# systemctl stop firewalld;setenforce 0
# vim /etc/hosts
192.168.1.18 k8s-master
192.168.1.22 k8s-node1
192.168.1.25 k8s-node2
軟件版本:
Docker 18.09.0-ce
Kubernetes 1.11
服務(wù)器角色、IP、組件:
k8s-master
192.168.1.18 kube-apiserver,kube-controller-manager,kube-scheduler,etcd
k8s-node1
192.168.1.22 kubelet,kube-proxy,docker,flannel,etcd
k8s-node2
192.168.1.25 kubelet,kube-proxy,docker,flannel,etcd
因我電腦配置較低 etcd 配置在了三臺(tái)服務(wù)器上,實(shí)際生產(chǎn)環(huán)境中應(yīng)該部署在單獨(dú)的三臺(tái)服務(wù)器
2. 部署Etcd集群
使用cfssl來(lái)生成自簽證書(shū),任何機(jī)器都行,證書(shū)這塊兒知道怎么生成、怎么用即可,暫且不用過(guò)多研究。
#下載cfssl工具
[root@k8s-master k8s]# wget https://pkg.cfssl.org/R1.2/cfssl_linux-amd64
[root@k8s-master k8s]# wget https://pkg.cfssl.org/R1.2/cfssljson_linux-amd64
[root@k8s-master k8s]# wget https://pkg.cfssl.org/R1.2/cfssl-certinfo_linux-amd64
[root@k8s-master k8s]# ls
cfssl-certinfo_linux-amd64 cfssljson_linux-amd64 cfssl_linux-amd64
[root@k8s-master k8s]# chmod +x cfssl*
[root@k8s-master k8s]# mv cfssl_linux-amd64 /usr/local/bin/cfssl
[root@k8s-master k8s]# mv cfssljson_linux-amd64 /usr/local/bin/cfssljson
[root@k8s-master k8s]# mv cfssl-certinfo_linux-amd64 /usr/bin/cfssl-certinfo
#生成Etcd證書(shū)
[root@k8s-master k8s]# vim ca-config.json
[root@k8s-master k8s]# cat ca-config.json
{
"signing": {
"default": {
"expiry": "87600h"
},
"profiles": {
"www": {
"expiry": "87600h",
"usages": [
"signing",
"key encipherment",
"server auth",
"client auth"
]
}
}
}
}
[root@k8s-master k8s]# vim ca-csr.json
[root@k8s-master k8s]# cat ca-csr.json
{
"CN": "etcd CA",
"key": {
"algo": "rsa",
"size": 2048
},
"names": [
{
"C": "CN",
"L": "Beijing",
"ST": "Beijing"
}
]
}
[root@k8s-master k8s]# vim server-csr.json
[root@k8s-master k8s]# cat server-csr.json #IP填寫(xiě)etcd集群的IP
{
"CN": "etcd",
"hosts": [
"192.168.1.18",
"192.168.1.22",
"192.168.1.25"
],
"key": {
"algo": "rsa",
"size": 2048
},
"names": [
{
"C": "CN",
"L": "BeiJing",
"ST": "BeiJing"
}
]
}
#生成證書(shū)
[root@k8s-master k8s]# cfssl gencert -initca ca-csr.json | cfssljson -bare ca -
[root@k8s-master k8s]# cfssl gencert -ca=ca.pem -ca-key=ca-key.pem -config=ca-config.json -profile=www server-csr.json | cfssljson -bare server
[root@k8s-master k8s]# ls *pem
ca-key.pem ca.pem server-key.pem server.pem
#安裝Etcd,三臺(tái)都配置
# wget https://github.com/etcd-io/etcd/releases/download/v3.2.12/etcd-v3.2.12-linux-amd64.tar.gz
# mkdir /opt/etcd/{bin,cfg,ssl} -p
# tar zxvf etcd-v3.2.12-linux-amd64.tar.gz
# mv etcd-v3.2.12-linux-amd64/{etcd,etcdctl} /opt/etcd/bin/
#創(chuàng)建etcd配置文件,三臺(tái)都配置:IP要寫(xiě)當(dāng)前的
[root@k8s-master ~]# vim /opt/etcd/cfg/etcd
[root@k8s-master ~]# cat /opt/etcd/cfg/etcd
#[Member]
ETCD_NAME="etcd01" #節(jié)點(diǎn)名稱(chēng) 修改
ETCD_DATA_DIR="/var/lib/etcd/default.etcd" #數(shù)據(jù)目錄
ETCD_LISTEN_PEER_URLS="https://192.168.1.18:2380" #集群通信監(jiān)聽(tīng)地址 修改
ETCD_LISTEN_CLIENT_URLS="https://192.168.1.18:2379" #客戶端訪問(wèn)監(jiān)聽(tīng)地址 修改
#[Clustering]
ETCD_INITIAL_ADVERTISE_PEER_URLS="https://192.168.1.18:2380" #集群通告地址 修改
ETCD_ADVERTISE_CLIENT_URLS="https://192.168.1.18:2379" #客戶端通告地址 修改
ETCD_INITIAL_CLUSTER="etcd01=https://192.168.1.18:2380,etcd02=https://192.168.1.22:2380,etcd03=https://192.168.1.25:2380" #集群節(jié)點(diǎn)地址 修改名字和IP對(duì)應(yīng)
ETCD_INITIAL_CLUSTER_TOKEN="etcd-cluster" #集群Token
ETCD_INITIAL_CLUSTER_STATE="new" #加入集群的當(dāng)前狀態(tài),new是新集群,existing表示加入已有集群
#systemd管理etcd,三臺(tái)都配置
[root@k8s-master ~]# vim /usr/lib/systemd/system/etcd.service
[root@k8s-master ~]# cat /usr/lib/systemd/system/etcd.service
[Unit]
Description=Etcd Server
After=network.target
After=network-online.target
Wants=network-online.target
[Service]
Type=notify
EnvironmentFile=/opt/etcd/cfg/etcd
ExecStart=/opt/etcd/bin/etcd \
--name=${ETCD_NAME} \
--data-dir=${ETCD_DATA_DIR} \
--listen-peer-urls=${ETCD_LISTEN_PEER_URLS} \
--listen-client-urls=${ETCD_LISTEN_CLIENT_URLS},http://127.0.0.1:2379 \
--advertise-client-urls=${ETCD_ADVERTISE_CLIENT_URLS} \
--initial-advertise-peer-urls=${ETCD_INITIAL_ADVERTISE_PEER_URLS} \
--initial-cluster=${ETCD_INITIAL_CLUSTER} \
--initial-cluster-token=${ETCD_INITIAL_CLUSTER_TOKEN} \
--initial-cluster-state=new \
--cert-file=/opt/etcd/ssl/server.pem \
--key-file=/opt/etcd/ssl/server-key.pem \
--peer-cert-file=/opt/etcd/ssl/server.pem \
--peer-key-file=/opt/etcd/ssl/server-key.pem \
--trusted-ca-file=/opt/etcd/ssl/ca.pem \
--peer-trusted-ca-file=/opt/etcd/ssl/ca.pem
Restart=on-failure
LimitNOFILE=65536
[Install]
WantedBy=multi-user.target
#把剛才生成的證書(shū)拷貝到配置文件中的位置
[root@k8s-master ~]# cp /k8s/*pem /opt/etcd/ssl
#啟動(dòng)并設(shè)置開(kāi)啟啟動(dòng),三臺(tái)都配置
# systemctl start etcd
# systemctl enable etcd
#檢查etcd集群狀態(tài)
[root@k8s-master ~]# /opt/etcd/bin/etcdctl \
--ca-file=/opt/etcd/ssl/ca.pem --cert-file=/opt/etcd/ssl/server.pem --key-file=/opt/etcd/ssl/server-key.pem \
--endpoints="https://192.168.1.18:2379,https://192.168.1.22:2379,https://192.168.1.25:2379" \
cluster-health
cluster is healthy 輸出此行,集群部署成功
3. node節(jié)點(diǎn)安裝docker
# yum install -y yum-utils device-mapper-persistent-data lvm2
# yum-config-manager --add-repo https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo
# yum makecache fast
# yum -y install docker-ce
# systemctl start docker
# systemctl enable docker
# docker -v
Docker version 19.03.8, build afacb8b
4. 部署Flannel網(wǎng)絡(luò)
工作原理

#Falnnel要用etcd存儲(chǔ)自身一個(gè)子網(wǎng)信息,所以要保證能成功連接Etcd,寫(xiě)入預(yù)定義子網(wǎng)段,注意修改IP
[root@k8s-master ~]# cd /opt/etcd/ssl/
[root@k8s-master ssl]# ls
ca-key.pem ca.pem server-key.pem server.pem
[root@k8s-master ssl]# /opt/etcd/bin/etcdctl \
> --ca-file=ca.pem --cert-file=server.pem --key-file=server-key.pem \
> --endpoints="https://192.168.1.18:2379,https://192.168.1.22:2379,https://192.168.1.25:2379" \
> set /coreos.com/network/config '{ "Network": "172.17.0.0/16", "Backend": {"Type": "vxlan"}}'
#安裝Flannel,node節(jié)點(diǎn)操作
# wget https://github.com/coreos/flannel/releases/download/v0.10.0/flannel-v0.10.0-linux-amd64.tar.gz
# tar xzvf flannel-v0.10.0-linux-amd64.tar.gz
# mkdir -p /opt/kubernetes/bin
# mv flanneld mk-docker-opts.sh /opt/kubernetes/bin
#配置Flannel,node節(jié)點(diǎn)操作
# mkdir -p /opt/kubernetes/cfg/
# vim /opt/kubernetes/cfg/flanneld
# vim /opt/kubernetes/cfg/flanneld
# cat /opt/kubernetes/cfg/flanneld #注意修改IP
FLANNEL_OPTIONS="--etcd-endpoints=https://192.168.1.18:2379,https://192.168.1.22:2379,https://192.168.1.25:2379 -etcd-cafile=/opt/etcd/ssl/ca.pem -etcd-certfile=/opt/etcd/ssl/server.pem -etcd-keyfile=/opt/etcd/ssl/server-key.pem"
#systemd管理Flannel,node節(jié)點(diǎn)操作
# vim /usr/lib/systemd/system/flanneld.service
# cat /usr/lib/systemd/system/flanneld.service
[Unit]
Description=Flanneld overlay address etcd agent
After=network-online.target network.target
Before=docker.service
[Service]
Type=notify
EnvironmentFile=/opt/kubernetes/cfg/flanneld
ExecStart=/opt/kubernetes/bin/flanneld --ip-masq $FLANNEL_OPTIONS
ExecStartPost=/opt/kubernetes/bin/mk-docker-opts.sh -k DOCKER_NETWORK_OPTIONS -d /run/flannel/subnet.env
Restart=on-failure
[Install]
WantedBy=multi-user.target
#配置Docker啟動(dòng)指定子網(wǎng)段,node節(jié)點(diǎn)操作
# vim /usr/lib/systemd/system/docker.service
# cat /usr/lib/systemd/system/docker.service
[Unit]
Description=Docker Application Container Engine
Documentation=https://docs.docker.com
After=network-online.target firewalld.service
Wants=network-online.target
[Service]
Type=notify
EnvironmentFile=/run/flannel/subnet.env
ExecStart=/usr/bin/dockerd $DOCKER_NETWORK_OPTIONS
ExecReload=/bin/kill -s HUP $MAINPID
LimitNOFILE=infinity
LimitNPROC=infinity
LimitCORE=infinity
TimeoutStartSec=0
Delegate=yes
KillMode=process
Restart=on-failure
StartLimitBurst=3
StartLimitInterval=60s
[Install]
WantedBy=multi-user.target
#將證書(shū)拷貝到node節(jié)點(diǎn)
[root@k8s-master ~]# scp /k8s/*pem k8s-node1:/opt/etcd/ssl
[root@k8s-master ~]# scp /k8s/*pem k8s-node2:/opt/etcd/ssl
#重啟flannel和docker,node節(jié)點(diǎn)操作
# systemctl daemon-reload
# systemctl start flanneld
# systemctl enable flanneld
# systemctl restart docker
#檢查是否生效,node節(jié)點(diǎn)操作
[root@k8s-node1 ~]# ps -ef |grep docker
root 12103 1 2 18:07 ? 00:00:00 /usr/bin/dockerd --bip=172.17.90.1/24 --ip-masq=false --mtu=1450
root 12240 10550 0 18:07 pts/0 00:00:00 grep --color=auto docker
[root@k8s-node2 ~]# ps -ef |grep docker
root 12112 1 1 18:07 ? 00:00:00 /usr/bin/dockerd --bip=172.17.96.1/24 --ip-masq=false --mtu=1450
root 12267 1314 0 18:08 pts/0 00:00:00 grep --color=auto docker
#確保node節(jié)點(diǎn)的docker0與flannel.1在同一網(wǎng)段,node節(jié)點(diǎn)網(wǎng)段互相不一樣
[root@k8s-node1 ~]# ifconfig docker0 | grep inet | head -n 1 | awk '{print $2}'
172.17.90.1
[root@k8s-node1 ~]# ifconfig flannel.1 | grep inet | head -n 1 | awk '{print $2}'
172.17.90.0
[root@k8s-node2 ~]# ifconfig docker0 | grep inet | head -n 1 | awk '{print $2}'
172.17.96.1
[root@k8s-node2 ~]# ifconfig flannel.1 | grep inet | head -n 1 | awk '{print $2}'
172.17.96.0
#node節(jié)點(diǎn)互相ping測(cè)試
[root@k8s-node1 ~]# ping 172.17.96.1
[root@k8s-node2 ~]# ping 172.17.90.1
#ping通Flannel部署成功
5. 在Master節(jié)點(diǎn)部署組件
在部署Kubernetes之前一定要確保etcd、flannel、docker是正常工作的。
5.1 生成證書(shū)
[root@k8s-master ~]# cd /k8s/
[root@k8s-master k8s]# ls
ca-config.json ca.csr ca-csr.json ca-key.pem ca.pem server.csr server-csr.json server-key.pem server.pem
[root@k8s-master k8s]# mkdir etcdsslbk
[root@k8s-master k8s]# mv * etcdsslbk/
mv: 無(wú)法將目錄"etcdsslbk" 移動(dòng)至自身的子目錄"etcdsslbk/etcdsslbk" 下
[root@k8s-master k8s]# ls
etcdsslbk
[root@k8s-master k8s]# ls etcdsslbk/
ca-config.json ca.csr ca-csr.json ca-key.pem ca.pem server.csr server-csr.json server-key.pem server.pem
[root@k8s-master k8s]# vim ca-config.json
[root@k8s-master k8s]# cat ca-config.json
{
"signing": {
"default": {
"expiry": "87600h"
},
"profiles": {
"kubernetes": {
"expiry": "87600h",
"usages": [
"signing",
"key encipherment",
"server auth",
"client auth"
]
}
}
}
}
[root@k8s-master k8s]# vim ca-csr.json
[root@k8s-master k8s]# cat ca-csr.json
{
"CN": "kubernetes",
"key": {
"algo": "rsa",
"size": 2048
},
"names": [
{
"C": "CN",
"L": "Beijing",
"ST": "Beijing",
"O": "k8s",
"OU": "System"
}
]
}
[root@k8s-master k8s]# cfssl gencert -initca ca-csr.json | cfssljson -bare ca -
#生成apiserver證書(shū)
[root@k8s-master k8s]# vim server-csr.json
[root@k8s-master k8s]# cat server-csr.json
{
"CN": "kubernetes",
"hosts": [
"192.168.1.1", #這個(gè)是后邊dns要用的虛擬網(wǎng)絡(luò)的網(wǎng)關(guān)
"127.0.0.1",
"192.168.1.18", #k8s集群IP
"192.168.1.22", #k8s集群IP
"192.168.1.25", #k8s集群IP
"kubernetes",
"kubernetes.default",
"kubernetes.default.svc",
"kubernetes.default.svc.cluster",
"kubernetes.default.svc.cluster.local"
],
"key": {
"algo": "rsa",
"size": 2048
},
"names": [
{
"C": "CN",
"L": "BeiJing",
"ST": "BeiJing",
"O": "k8s",
"OU": "System"
}
]
}
[root@k8s-master k8s]# cfssl gencert -ca=ca.pem -ca-key=ca-key.pem -config=ca-config.json -profile=kubernetes server-csr.json | cfssljson -bare server
#生成kube-proxy證書(shū)
[root@k8s-master k8s]# vim kube-proxy-csr.json
[root@k8s-master k8s]# cat kube-proxy-csr.json
{
"CN": "system:kube-proxy",
"hosts": [],
"key": {
"algo": "rsa",
"size": 2048
},
"names": [
{
"C": "CN",
"L": "BeiJing",
"ST": "BeiJing",
"O": "k8s",
"OU": "System"
}
]
}
[root@k8s-master k8s]# cfssl gencert -ca=ca.pem -ca-key=ca-key.pem -config=ca-config.json -profile=kubernetes kube-proxy-csr.json | cfssljson -bare kube-proxy
[root@k8s-master k8s]# ls *.pem
ca-key.pem ca.pem kube-proxy-key.pem kube-proxy.pem server-key.pem server.pem
5.2 部署apiserver組件
瀏覽器訪問(wèn)此鏈接下載包,傳到服務(wù)器(https://dl.k8s.io/v1.11.0/kubernetes-server-linux-amd64.tar.gz)
[root@k8s-master ~]# mkdir /opt/kubernetes/{bin,cfg,ssl} -p
[root@k8s-master ~]# tar zxvf kubernetes-server-linux-amd64.tar.gz
[root@k8s-master ~]# cd kubernetes/server/bin
[root@k8s-master bin]# cp kube-apiserver kube-scheduler kube-controller-manager kubectl /opt/kubernetes/bin
#將生成的證書(shū)拷貝到master對(duì)應(yīng)目錄
[root@k8s-master ~]# cd /k8s/
[root@k8s-master k8s]# cp server.pem server-key.pem ca.pem ca-key.pem /opt/kubernetes/ssl/
#創(chuàng)建token文件
[root@k8s-master k8s]# vim /opt/kubernetes/cfg/token.csv
[root@k8s-master k8s]# cat /opt/kubernetes/cfg/token.csv
674c457d4dcf2eefe4920d7dbb6b0ddc,kubelet-bootstrap,10001,"system:kubelet-bootstrap"
#第一列:隨機(jī)字符串,自己可生成,第二列:用戶名,第三列:UID,第四列:用戶組。
#創(chuàng)建apiserver配置文件
[root@k8s-master k8s]# vim /opt/kubernetes/cfg/kube-apiserver
[root@k8s-master k8s]# cat /opt/kubernetes/cfg/kube-apiserver
KUBE_APISERVER_OPTS="--logtostderr=true \
--v=4 \
--etcd-servers=https://192.168.1.18:2379,https://192.168.1.22:2379,https://192.168.1.25:2379 \
--bind-address=192.168.1.18 \
--secure-port=6443 \
--advertise-address=192.168.1.18 \
--allow-privileged=true \
--service-cluster-ip-range=192.168.1.0/24 \
--enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,ResourceQuota,NodeRestriction \
--authorization-mode=RBAC,Node \
--enable-bootstrap-token-auth \
--token-auth-file=/opt/kubernetes/cfg/token.csv \
--service-node-port-range=30000-50000 \
--tls-cert-file=/opt/kubernetes/ssl/server.pem \
--tls-private-key-file=/opt/kubernetes/ssl/server-key.pem \
--client-ca-file=/opt/kubernetes/ssl/ca.pem \
--service-account-key-file=/opt/kubernetes/ssl/ca-key.pem \
--etcd-cafile=/opt/etcd/ssl/ca.pem \
--etcd-certfile=/opt/etcd/ssl/server.pem \
--etcd-keyfile=/opt/etcd/ssl/server-key.pem"
#參數(shù)說(shuō)明:
--logtostderr 啟用日志
--v 日志等級(jí)
--etcd-servers etcd集群地址
--bind-address 監(jiān)聽(tīng)地址
--secure-port https安全端口
--advertise-address 集群通告地址
--allow-privileged 啟用授權(quán)
--service-cluster-ip-range Service虛擬IP地址段
--enable-admission-plugins 準(zhǔn)入控制模塊
--authorization-mode 認(rèn)證授權(quán),啟用RBAC授權(quán)和節(jié)點(diǎn)自管理
--enable-bootstrap-token-auth 啟用TLS bootstrap功能,后面會(huì)講到
--token-auth-file token文件
--service-node-port-range Service Node類(lèi)型默認(rèn)分配端口范圍
#systemd管理apiserver
[root@k8s-master k8s]# vim /usr/lib/systemd/system/kube-apiserver.service
[root@k8s-master k8s]# cat /usr/lib/systemd/system/kube-apiserver.service
[Unit]
Description=Kubernetes API Server
Documentation=https://github.com/kubernetes/kubernetes
[Service]
EnvironmentFile=-/opt/kubernetes/cfg/kube-apiserver
ExecStart=/opt/kubernetes/bin/kube-apiserver $KUBE_APISERVER_OPTS
Restart=on-failure
[Install]
WantedBy=multi-user.target
#啟動(dòng)apiserver
[root@k8s-master k8s]# systemctl daemon-reload
[root@k8s-master k8s]# systemctl start kube-apiserver
[root@k8s-master k8s]# systemctl enable kube-apiserver
5.3 部署schduler組件
[root@k8s-master k8s]# vim /opt/kubernetes/cfg/kube-scheduler
[root@k8s-master k8s]# cat /opt/kubernetes/cfg/kube-scheduler
KUBE_SCHEDULER_OPTS="--logtostderr=true \
--v=4 \
--master=127.0.0.1:8080 \
--leader-elect"
#參數(shù)說(shuō)明:
--master 連接本地apiserver
--leader-elect 當(dāng)該組件啟動(dòng)多個(gè)時(shí),自動(dòng)選舉(HA)
#systemd管理schduler組件
[root@k8s-master k8s]# vim /usr/lib/systemd/system/kube-scheduler.service
[root@k8s-master k8s]# cat /usr/lib/systemd/system/kube-scheduler.service
[Unit]
Description=Kubernetes Scheduler
Documentation=https://github.com/kubernetes/kubernetes
[Service]
EnvironmentFile=-/opt/kubernetes/cfg/kube-scheduler
ExecStart=/opt/kubernetes/bin/kube-scheduler $KUBE_SCHEDULER_OPTS
Restart=on-failure
[Install]
WantedBy=multi-user.target
#啟動(dòng)
[root@k8s-master k8s]# systemctl daemon-reload
[root@k8s-master k8s]# systemctl start kube-scheduler
[root@k8s-master k8s]# systemctl enable kube-scheduler
5.4 部署controller-manager組件
[root@k8s-master k8s]# vim /opt/kubernetes/cfg/kube-controller-manager
[root@k8s-master k8s]# cat /opt/kubernetes/cfg/kube-controller-manager
KUBE_CONTROLLER_MANAGER_OPTS="--logtostderr=true \
--v=4 \
--master=127.0.0.1:8080 \
--leader-elect=true \
--address=127.0.0.1 \
--service-cluster-ip-range=192.168.1.0/24 \
--cluster-name=kubernetes \
--cluster-signing-cert-file=/opt/kubernetes/ssl/ca.pem \
--cluster-signing-key-file=/opt/kubernetes/ssl/ca-key.pem \
--root-ca-file=/opt/kubernetes/ssl/ca.pem \
--service-account-private-key-file=/opt/kubernetes/ssl/ca-key.pem"
#systemd管理controller-manager組件
[root@k8s-master k8s]# vim /usr/lib/systemd/system/kube-controller-manager.service
[root@k8s-master k8s]# cat /usr/lib/systemd/system/kube-controller-manager.service
[Unit]
Description=Kubernetes Controller Manager
Documentation=https://github.com/kubernetes/kubernetes
[Service]
EnvironmentFile=-/opt/kubernetes/cfg/kube-controller-manager
ExecStart=/opt/kubernetes/bin/kube-controller-manager $KUBE_CONTROLLER_MANAGER_OPTS
Restart=on-failure
[Install]
WantedBy=multi-user.target
#啟動(dòng)
[root@k8s-master k8s]# systemctl daemon-reload
[root@k8s-master k8s]# systemctl start kube-controller-manager
[root@k8s-master k8s]# systemctl enable kube-controller-manager
5.5 通過(guò)kubectl工具查看當(dāng)前集群組件狀態(tài)
[root@k8s-master k8s]# /opt/kubernetes/bin/kubectl get cs
NAME STATUS MESSAGE ERROR
controller-manager Healthy ok
scheduler Healthy ok
etcd-2 Healthy {"health": "true"}
etcd-1 Healthy {"health": "true"}
etcd-0 Healthy {"health": "true"}
如上輸出說(shuō)明組件都正常
6. 在Node節(jié)點(diǎn)部署組件
Master apiserver啟用TLS認(rèn)證后,Node節(jié)點(diǎn)kubelet組件想要加入集群,必須使用CA簽發(fā)的有效證書(shū)才能與apiserver通信,當(dāng)Node節(jié)點(diǎn)很多時(shí),簽署證書(shū)是一件很繁瑣的事情,因此有了TLS Bootstrapping機(jī)制,kubelet會(huì)以一個(gè)低權(quán)限用戶自動(dòng)向apiserver申請(qǐng)證書(shū),kubelet的證書(shū)由apiserver動(dòng)態(tài)簽署。
6.1 master節(jié)點(diǎn)操作
#將kubelet-bootstrap用戶綁定到系統(tǒng)集群角色
[root@k8s-master k8s]# /opt/kubernetes/bin/kubectl create clusterrolebinding kubelet-bootstrap \
--clusterrole=system:node-bootstrapper \
--user=kubelet-bootstrap
#創(chuàng)建kubeconfig文件,在生成kubernetes證書(shū)的目錄下執(zhí)行以下命令生成kubeconfig文件:
#指定apiserver 內(nèi)網(wǎng)負(fù)載均衡地址
[root@k8s-master k8s]# KUBE_APISERVER="https://192.168.1.18:6443"
[root@k8s-master k8s]# BOOTSTRAP_TOKEN=674c457d4dcf2eefe4920d7dbb6b0ddc
#設(shè)置集群參數(shù)
[root@k8s-master k8s]# /opt/kubernetes/bin/kubectl config set-cluster kubernetes \
--certificate-authority=./ca.pem \
--embed-certs=true \
--server=${KUBE_APISERVER} \
--kubeconfig=bootstrap.kubeconfig
#設(shè)置客戶端認(rèn)證參數(shù)
[root@k8s-master k8s]# /opt/kubernetes/bin/kubectl config set-credentials kubelet-bootstrap \
--token=${BOOTSTRAP_TOKEN} \
--kubeconfig=bootstrap.kubeconfig
#設(shè)置上下文參數(shù)
[root@k8s-master k8s]# /opt/kubernetes/bin/kubectl config set-context default \
--cluster=kubernetes \
--user=kubelet-bootstrap \
--kubeconfig=bootstrap.kubeconfig
#設(shè)置默認(rèn)上下文
[root@k8s-master k8s]# /opt/kubernetes/bin/kubectl config use-context default --kubeconfig=bootstrap.kubeconfig
#創(chuàng)建kube-proxy kubeconfig文件
[root@k8s-master k8s]# /opt/kubernetes/bin/kubectl config set-cluster kubernetes \
--certificate-authority=./ca.pem \
--embed-certs=true \
--server=${KUBE_APISERVER} \
--kubeconfig=kube-proxy.kubeconfig
[root@k8s-master k8s]# /opt/kubernetes/bin/kubectl config set-credentials kube-proxy \
--client-certificate=./kube-proxy.pem \
--client-key=./kube-proxy-key.pem \
--embed-certs=true \
--kubeconfig=kube-proxy.kubeconfig
[root@k8s-master k8s]# /opt/kubernetes/bin/kubectl config set-context default \
--cluster=kubernetes \
--user=kube-proxy \
--kubeconfig=kube-proxy.kubeconfig
[root@k8s-master k8s]# /opt/kubernetes/bin/kubectl config use-context default --kubeconfig=kube-proxy.kubeconfig
#將這兩個(gè)文件拷貝到Node節(jié)點(diǎn)/opt/kubernetes/cfg/目錄下。
[root@k8s-master k8s]# scp bootstrap.kubeconfig kube-proxy.kubeconfig k8s-node1:/opt/kubernetes/cfg/
[root@k8s-master k8s]# scp bootstrap.kubeconfig kube-proxy.kubeconfig k8s-node2:/opt/kubernetes/cfg/
#部署kubelet組件,將前面下載的二進(jìn)制包中的kubelet和kube-proxy拷貝到Node節(jié)點(diǎn)/opt/kubernetes/bin目錄下。
[root@k8s-master k8s]# cd /root/kubernetes/server/bin/
[root@k8s-master bin]# scp kubelet kube-proxy k8s-node1:/opt/kubernetes/bin/
[root@k8s-master bin]# scp kubelet kube-proxy k8s-node2:/opt/kubernetes/bin/
6.2 部署kubelet組件
所有node節(jié)點(diǎn)操作
#創(chuàng)建kubelet配置文件
[root@k8s-node1 ~]# vim /opt/kubernetes/cfg/kubelet
[root@k8s-node1 ~]# cat /opt/kubernetes/cfg/kubelet
KUBELET_OPTS="--logtostderr=true \
--v=4 \
--hostname-override=192.168.1.22 \ #修改為本機(jī)為IP
--kubeconfig=/opt/kubernetes/cfg/kubelet.kubeconfig \
--bootstrap-kubeconfig=/opt/kubernetes/cfg/bootstrap.kubeconfig \
--config=/opt/kubernetes/cfg/kubelet.config \
--cert-dir=/opt/kubernetes/ssl \
--pod-infra-container-image=registry.cn-hangzhou.aliyuncs.com/google-containers/pause-amd64:3.0"
#參數(shù)說(shuō)明:
--hostname-override 在集群中顯示的主機(jī)名
--kubeconfig 指定kubeconfig文件位置,會(huì)自動(dòng)生成
--bootstrap-kubeconfig 指定剛才生成的bootstrap.kubeconfig文件
--cert-dir 頒發(fā)證書(shū)存放位置
--pod-infra-container-image 管理Pod網(wǎng)絡(luò)的鏡像
#其中/opt/kubernetes/cfg/kubelet.config配置文件如下
[root@k8s-node1 ~]# vim /opt/kubernetes/cfg/kubelet.config
[root@k8s-node1 ~]# cat /opt/kubernetes/cfg/kubelet.config
kind: KubeletConfiguration
apiVersion: kubelet.config.k8s.io/v1beta1
address: 192.168.1.22 #修改為本機(jī)為IP
port: 10250
readOnlyPort: 10255
cgroupDriver: cgroupfs
clusterDNS: ["192.168.1.2"]
clusterDomain: cluster.local.
failSwapOn: false
authentication:
anonymous:
enabled: true
webhook:
enabled: false
#systemd管理kubelet組件
[root@k8s-node1 ~]# vim /usr/lib/systemd/system/kubelet.service
[root@k8s-node1 ~]# cat /usr/lib/systemd/system/kubelet.service
[Unit]
Description=Kubernetes Kubelet
After=docker.service
Requires=docker.service
[Service]
EnvironmentFile=/opt/kubernetes/cfg/kubelet
ExecStart=/opt/kubernetes/bin/kubelet $KUBELET_OPTS
Restart=on-failure
KillMode=process
[Install]
WantedBy=multi-user.target
#啟動(dòng)
[root@k8s-node1 ~]# systemctl daemon-reload
[root@k8s-node1 ~]# systemctl start kubelet
[root@k8s-node1 ~]# systemctl enable kubelet
#在Master審批Node加入集群
[root@k8s-master bin]# /opt/kubernetes/bin/kubectl get csr
NAME AGE REQUESTOR CONDITION
node-csr-Oecfo2IVLnnCGoYqhQ3f6q7FbN0C2Dr7c0o8j-6v2rI 2m kubelet-bootstrap Pending
node-csr-tRpwDHVhxW-9DxLkW_hu2XErEs1LBveGaah9_cREJrE 2m kubelet-bootstrap Pending
[root@k8s-master bin]# /opt/kubernetes/bin/kubectl certificate approve node-csr-Oecfo2IVLnnCGoYqhQ3f6q7FbN0C2Dr7c0o8j-6v2rI
[root@k8s-master bin]# /opt/kubernetes/bin/kubectl certificate approve node-csr-tRpwDHVhxW-9DxLkW_hu2XErEs1LBveGaah9_cREJrE
[root@k8s-master bin]# /opt/kubernetes/bin/kubectl get csr
NAME AGE REQUESTOR CONDITION
node-csr-Oecfo2IVLnnCGoYqhQ3f6q7FbN0C2Dr7c0o8j-6v2rI 3m kubelet-bootstrap Approved,Issued
node-csr-tRpwDHVhxW-9DxLkW_hu2XErEs1LBveGaah9_cREJrE 2m kubelet-bootstrap Approved,Issued
[root@k8s-master bin]# /opt/kubernetes/bin/kubectl get node
NAME STATUS ROLES AGE VERSION
192.168.1.22 Ready <none> 6s v1.11.0
192.168.1.25 Ready <none> 13s v1.11.0
6.3 部署kube-proxy組件
所有node節(jié)點(diǎn)操作
#創(chuàng)建kube-proxy配置文件
[root@k8s-node1 ~]# vim /opt/kubernetes/cfg/kube-proxy
[root@k8s-node1 ~]# cat /opt/kubernetes/cfg/kube-proxy
KUBE_PROXY_OPTS="--logtostderr=true \
--v=4 \
--hostname-override=192.168.1.22 \ #修改為本機(jī)IP
--cluster-cidr=192.168.1.0/24 \
--kubeconfig=/opt/kubernetes/cfg/kube-proxy.kubeconfig"
#systemd管理kube-proxy組件
[root@k8s-node1 ~]# vim /usr/lib/systemd/system/kube-proxy.service
[root@k8s-node1 ~]# cat /usr/lib/systemd/system/kube-proxy.service
[Unit]
Description=Kubernetes Proxy
After=network.target
[Service]
EnvironmentFile=-/opt/kubernetes/cfg/kube-proxy
ExecStart=/opt/kubernetes/bin/kube-proxy $KUBE_PROXY_OPTS
Restart=on-failure
[Install]
WantedBy=multi-user.target
#啟動(dòng)
[root@k8s-node1 ~]# systemctl daemon-reload
[root@k8s-node1 ~]# systemctl start kube-proxy
[root@k8s-node1 ~]# systemctl enable kube-proxy
7. 查看集群狀態(tài)
master查看
[root@k8s-master bin]# /opt/kubernetes/bin/kubectl get node
NAME STATUS ROLES AGE VERSION
192.168.1.22 Ready <none> 8m v1.11.0
192.168.1.25 Ready <none> 8m v1.11.0
[root@k8s-master bin]# /opt/kubernetes/bin/kubectl get cs
NAME STATUS MESSAGE ERROR
scheduler Healthy ok
controller-manager Healthy ok
etcd-1 Healthy {"health": "true"}
etcd-2 Healthy {"health": "true"}
etcd-0 Healthy {"health": "true"}
8. 運(yùn)行一個(gè)測(cè)試示例
創(chuàng)建一個(gè)Nginx Web,判斷集群是否正常工作
[root@k8s-master bin]# /opt/kubernetes/bin/kubectl run nginx --image=nginx --replicas=3
[root@k8s-master bin]# /opt/kubernetes/bin/kubectl expose deployment nginx --port=88 --target-port=80 --type=NodePort
查看Pod,Service:
[root@k8s-master bin]# /opt/kubernetes/bin/kubectl get pods
NAME READY STATUS RESTARTS AGE
nginx-64f497f8fd-fjgt2 1/1 Running 0 3m
nginx-64f497f8fd-gmstq 1/1 Running 0 3m
nginx-64f497f8fd-q6wk9 1/1 Running 0 3m
查看pod詳細(xì)信息:
[root@k8s-master bin]# /opt/kubernetes/bin/kubectl describe pod nginx-64f497f8fd-fjgt2
[root@k8s-master bin]# /opt/kubernetes/bin/kubectl get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kubernetes ClusterIP 192.168.1.1 <none> 443/TCP 3m
nginx NodePort 192.168.1.175 <none> 88:38696/TCP 3m
[root@k8s-master bin]# curl -I 192.168.1.22:38696
或者
瀏覽器訪問(wèn):http://192.168.1.22:38696 測(cè)試

9. 部署Dashboard(Web UI)
部署UI有三個(gè)文件:
* dashboard-deployment.yaml // 部署Pod,提供Web服務(wù)
* dashboard-rbac.yaml // 授權(quán)訪問(wèn)apiserver獲取信息
* dashboard-service.yaml // 發(fā)布服務(wù),提供對(duì)外訪問(wèn)
[root@k8s-master ~]# mkdir /k8s/dashboard
[root@k8s-master ~]# cd /k8s/dashboard
[root@k8s-master dashboard]# vim dashboard-deployment.yaml
[root@k8s-master dashboard]# cat dashboard-deployment.yaml
apiVersion: apps/v1beta2
kind: Deployment
metadata:
name: kubernetes-dashboard
namespace: kube-system
labels:
k8s-app: kubernetes-dashboard
kubernetes.io/cluster-service: "true"
addonmanager.kubernetes.io/mode: Reconcile
spec:
selector:
matchLabels:
k8s-app: kubernetes-dashboard
template:
metadata:
labels:
k8s-app: kubernetes-dashboard
annotations:
scheduler.alpha.kubernetes.io/critical-pod: ''
spec:
serviceAccountName: kubernetes-dashboard
containers:
- name: kubernetes-dashboard
image: registry.cn-hangzhou.aliyuncs.com/kube_containers/kubernetes-dashboard-amd64:v1.8.1
resources:
limits:
cpu: 100m
memory: 300Mi
requests:
cpu: 100m
memory: 100Mi
ports:
- containerPort: 9090
protocol: TCP
livenessProbe:
httpGet:
scheme: HTTP
path: /
port: 9090
initialDelaySeconds: 30
timeoutSeconds: 30
tolerations:
- key: "CriticalAddonsOnly"
operator: "Exists"
[root@k8s-master dashboard]# vim dashboard-rbac.yaml
[root@k8s-master dashboard]# cat dashboard-rbac.yaml
apiVersion: v1
kind: ServiceAccount
metadata:
labels:
k8s-app: kubernetes-dashboard
addonmanager.kubernetes.io/mode: Reconcile
name: kubernetes-dashboard
namespace: kube-system
---
kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:
name: kubernetes-dashboard-minimal
namespace: kube-system
labels:
k8s-app: kubernetes-dashboard
addonmanager.kubernetes.io/mode: Reconcile
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: cluster-admin
subjects:
- kind: ServiceAccount
name: kubernetes-dashboard
namespace: kube-system
[root@k8s-master dashboard]# vim dashboard-service.yaml
[root@k8s-master dashboard]# cat dashboard-service.yaml
apiVersion: v1
kind: Service
metadata:
name: kubernetes-dashboard
namespace: kube-system
labels:
k8s-app: kubernetes-dashboard
kubernetes.io/cluster-service: "true"
addonmanager.kubernetes.io/mode: Reconcile
spec:
type: NodePort
selector:
k8s-app: kubernetes-dashboard
ports:
- port: 80
targetPort: 9090
#創(chuàng)建
[root@k8s-master dashboard]# /opt/kubernetes/bin/kubectl create -f dashboard-rbac.yaml
[root@k8s-master dashboard]# /opt/kubernetes/bin/kubectl create -f dashboard-deployment.yaml
[root@k8s-master dashboard]# /opt/kubernetes/bin/kubectl create -f dashboard-service.yaml
#等待數(shù)分鐘,查看資源狀態(tài)
[root@k8s-master dashboard]# /opt/kubernetes/bin/kubectl get all -n kube-system
#查看訪問(wèn)端口
[root@k8s-master dashboard]# /opt/kubernetes/bin/kubectl get svc -n kube-system
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kubernetes-dashboard NodePort 192.168.1.100 <none> 443:31209/TCP 1m
瀏覽器訪192.168.1.22:31209測(cè)試