這篇文章主要介紹kubernetes中Master節(jié)點如何安裝與配置,文中介紹的非常詳細,具有一定的參考價值,感興趣的小伙伴們一定要看完!
一:簡介
1.kubernetes master節(jié)點包含以下組件:kube-apiserver,kube-scheduler和kube-controller-manager。 這三個組件需要部署在同一臺機器上。 同時只能有一個kube-scheduler,kube-controller-manager進程處于工作狀態(tài),如果運行多個,則需要通過選舉產(chǎn)生一個leader.
2.在/etc/kubernetes/ssl目錄下,準備好可能用到的證書文件。
admin-key.pem admin.pem ca-key.pem ca.pem kube-proxy-key.pem,kube-proxy.pem kubernetes-key.pem kubernetes.pem
3.下載安裝文件 wget https://storage.googleapis.com/kubernetes-release/release/v1.8.5/kubernetes-server-linux-amd64.tar.gz
tar -xzvf kubernetes-server-linux-amd64.tar.gz
cd kubernetes
tar -xzvf kubernetes-src.tar.gz
復制二進制文件到指定目錄
cp -r server/bin/{kube-apiserver,kube-controller-manager,kube-scheduler,kubectl,kube-proxy,kubelet} /usrbin/
二:配置和啟動 kube-apiserver
1.service配置文件 /usr/lib/systemd/system/kube-apiserver.service
點擊(此處)折疊或打開
[Unit]
Description=Kubernetes API Service
Documentation=https://github.com/GoogleCloudPlatform/kubernetes
After=network.target
After=etcd.service
[Service]
EnvironmentFile=-/etc/kubernetes/config
EnvironmentFile=-/etc/kubernetes/apiserver
ExecStart=/usr/bin/kube-apiserver \
$KUBE_LOGTOSTDERR \
$KUBE_LOG_LEVEL \
$KUBE_ETCD_SERVERS \
$KUBE_API_ADDRESS \
$KUBE_API_PORT \
$KUBELET_PORT \
$KUBE_ALLOW_PRIV \
$KUBE_SERVICE_ADDRESSES \
$KUBE_ADMISSION_CONTROL \
$KUBE_API_ARGS
Restart=on-failure
Type=notify
LimitNOFILE=65536
[Install]
WantedBy=multi-user.target
2.配置文件/etc/kubernetes/config
點擊(此處)折疊或打開
###
# kubernetes system config
#
# The following values are used to configure various aspects of all
# kubernetes services, including
#
# kube-apiserver.service
# kube-controller-manager.service
# kube-scheduler.service
# kubelet.service
# kube-proxy.service
# logging to stderr means we get it in the systemd journal
KUBE_LOGTOSTDERR="--logtostderr=true"
# journal message level, 0 is debug
KUBE_LOG_LEVEL="--v=0"
# Should this cluster be allowed to run privileged docker containers
KUBE_ALLOW_PRIV="--allow-privileged=true"
# How the controller-manager, scheduler, and proxy find the apiserver
KUBE_MASTER="--master=http://10.116.137.196:8080"
該配置文件同時被kube-apiserver、kube-controller-manager、kubescheduler、kubelet、kube-proxy使用。
3.配置文件 /etc/kubernetes/apiserver
點擊(此處)折疊或打開
###
## kubernetes system config
##
## The following values are used to configure the kube-apiserver
##
#
## The address on the local server to listen to.
KUBE_API_ADDRESS="--advertise-address=10.116.137.196 --bind-address=10.116.137.196 --insecure-bind-address=10.116.137.196"
#
## The port on the local server to listen on.
#KUBE_API_PORT="--port=8080"
#
## Port minions listen on
#KUBELET_PORT="--kubelet-port=10250"
#
## Comma separated list of nodes in the etcd cluster
KUBE_ETCD_SERVERS="--etcd-servers=https://10.116.137.196:2379,https://10.116.82.28:2379,https://10.116.36.57:2379"
#
## Address range to use for services
KUBE_SERVICE_ADDRESSES="--service-cluster-ip-range=10.254.0.0/16"
#
## default admission control policies
KUBE_ADMISSION_CONTROL="--admission-control=ServiceAccount,NamespaceLifecycle,NamespaceExists,LimitRanger,ResourceQuota"
#
## Add your own!
KUBE_API_ARGS="--authorization-mode=RBAC --runtime-config=rbac.authorization.k8s.io/v1beta1 --kubelet-https=true --experimental-bootstrap-token-auth --token-auth-file=/etc/kubernetes/token.csv --service-node-port-range=30000-32767 --tls-cert-file=/etc/kubernetes/ssl/kubernetes.pem --tls-private-key-file=/etc/kubernetes/ssl/kubernetes-key.pem --client-ca-file=/etc/kubernetes/ssl/ca.pem --service-account-key-file=/etc/kubernetes/ssl/ca-key.pem --etcd-cafile=/etc/kubernetes/ssl/ca.pem --etcd-certfile=/etc/kubernetes/ssl/kubernetes.pem --etcd-keyfile=/etc/kubernetes/ssl/kubernetes-key.pem --enable-swagger-ui=true --apiserver-count=1 --audit-log-maxage=30 --audit-log-maxbackup=3 --audit-log-maxsize=100 --audit-log-path=/var/lib/audit.log --event-ttl=1h"
a. --authorization-mode=RBAC 指定在安全端口使用 RBAC 授權(quán)模式,拒絕未通過授權(quán)的請求;
b. kube-scheduler、kube-controller-manager 一般和 kube-apiserver 部署在同一臺機器上,它們使非安全端口和 kube-apiserver通信;
kubelet、kube-proxy、kubectl 部署在其它 Node 節(jié)點上,如果通過安全端?訪問 kube-apiserver,則必須先通過 TLS 證書認證,再通過
RBAC 授權(quán);
c. kube-proxy、kubectl 通過在使?的證書?指定相關(guān)的 User、Group來達到通過 RBAC 授權(quán)的?的;
d. 如果使用了 kubelet TLS Boostrap 機制,則不能再指定 --kubeletcertificate-authority 、 --kubelet-client-certificate 和 --kubelet-client-key 選項,否則后續(xù) kube-apiserver 校驗 kubelet 證
書時出現(xiàn) ”x509: certificate signed by unknown authority“ 錯誤;
e. --admission-control 值必須包含 ServiceAccount ;
f. --bind-address 不能為 127.0.0.1 ;
g. runtime-config 配置為 rbac.authorization.k8s.io/v1beta1 ,表示運行時的apiVersion;
h. --service-cluster-ip-range 指定 Service Cluster IP 地址段,該地址段不能路由可達;
i. 缺省情況下 kubernetes 對象保存在 etcd /registry 路徑下,可以通過 --etcd-prefix 參數(shù)進行調(diào)整;
4.啟動kube-apiserver
systemctl daemon-reload
systemctl enable kube-apiserver
systemctl start kube-apiserver
systemctl status kube-apiserver
三:配置和啟動 kube-controller-manager
1. 服務文件/usr/lib/systemd/system/kube-controller-manager.service
點擊(此處)折疊或打開
[Unit]
Description=Kubernetes Controller Manager
Documentation=https://github.com/GoogleCloudPlatform/kubernetes
[Service]
EnvironmentFile=-/etc/kubernetes/config
EnvironmentFile=-/etc/kubernetes/controller-manager
ExecStart=/usr/bin/kube-controller-manager \
$KUBE_LOGTOSTDERR \
$KUBE_LOG_LEVEL \
$KUBE_MASTER \
$KUBE_CONTROLLER_MANAGER_ARGS
Restart=on-failure
LimitNOFILE=65536
[Install]
WantedBy=multi-user.target
2.配置文件 /etc/kubernetes/controller-manager
點擊(此處)折疊或打開
###
# The following values are used to configure the kubernetes controller-manager
# defaults from config and apiserver should be adequate
# Add your own!
KUBE_CONTROLLER_MANAGER_ARGS="--address=127.0.0.1 --service-cluster-ip-range=10.254.0.0/16 --cluster-name=kubernetes --cluster-signing-cert-file=/etc/kubernetes/ssl/ca.pem --cluster-signing-key-file=/etc/kubernetes/ssl/ca-key.pem --service-account-private-key-file=/etc/kubernetes/ssl/ca-key.pem --root-ca-file=/etc/kubernetes/ssl/ca.pem --leader-elect=true"
a. --service-cluster-ip-range 參數(shù)指定 Cluster 中 Service 的CIDR范圍,該?絡在各 Node 間必須路由不可達,必須和 kube-apiserver中的參數(shù)一致;
b. --cluster-signing-* 指定的證書和私鑰文件用來簽名為 TLSBootStrap 創(chuàng)建的證書和私鑰;
c. --root-ca-file 用來對 kube-apiserver 證書進行校驗,指定該參數(shù)后,才會在Pod 容器的 ServiceAccount 中放置該 CA 證書文件;
d. --address 值必須為 127.0.0.1 ,因為當前 kube-apiserver 期望scheduler 和 controller-manager 在同一臺機器
3.啟動 kube-controller-manager
systemctl daemon-reload
systemctl enable kube-controller-manager
systemctl start kube-controller-manager
四:配置和啟動 kube-scheduler
1. 服務文件/usr/lib/systemd/system/kube-scheduler.service
點擊(此處)折疊或打開
[Unit]
Description=Kubernetes Scheduler Plugin
Documentation=https://github.com/GoogleCloudPlatform/kubernetes
[Service]
EnvironmentFile=-/etc/kubernetes/config
EnvironmentFile=-/etc/kubernetes/scheduler
ExecStart=/usr/bin/kube-scheduler \
$KUBE_LOGTOSTDERR \
$KUBE_LOG_LEVEL \
$KUBE_MASTER \
$KUBE_SCHEDULER_ARGS
Restart=on-failure
LimitNOFILE=65536
[Install]
WantedBy=multi-user.target
2. 配置文件/etc/kubernetes/scheduler
點擊(此處)折疊或打開
###
# kubernetes scheduler config
# default config should be adequate
# Add your own!
KUBE_SCHEDULER_ARGS="--leader-elect=true --address=127.0.0.1"
3.啟動 kube-scheduler
systemctl daemon-reload
systemctl enable kube-scheduler
systemctl start kube-scheduler
五:驗證 master 節(jié)點功能
以上是“kubernetes中Master節(jié)點如何安裝與配置”這篇文章的所有內(nèi)容,感謝各位的閱讀!希望分享的內(nèi)容對大家有幫助,更多相關(guān)知識,歡迎關(guān)注創(chuàng)新互聯(lián)行業(yè)資訊頻道!
網(wǎng)頁標題:kubernetes中Master節(jié)點如何安裝與配置-創(chuàng)新互聯(lián)
標題來源:http://aaarwkj.com/article22/dohpjc.html
成都網(wǎng)站建設公司_創(chuàng)新互聯(lián),為您提供外貿(mào)建站、云服務器、網(wǎng)站制作、手機網(wǎng)站建設、小程序開發(fā)、網(wǎng)頁設計公司
聲明:本網(wǎng)站發(fā)布的內(nèi)容(圖片、視頻和文字)以用戶投稿、用戶轉(zhuǎn)載內(nèi)容為主,如果涉及侵權(quán)請盡快告知,我們將會在第一時間刪除。文章觀點不代表本網(wǎng)站立場,如需處理請聯(lián)系客服。電話:028-86922220;郵箱:631063699@qq.com。內(nèi)容未經(jīng)允許不得轉(zhuǎn)載,或轉(zhuǎn)載時需注明來源: 創(chuàng)新互聯(lián)
猜你還喜歡下面的內(nèi)容