K8s 1.6.2 安裝配置-master集群(三）

kubernetes master 節(jié)點(diǎn)包含的組件：

  • kube-apiserver
  • kube-scheduler
  • kube-controller-manager
    目前這三個(gè)組件需要部署在同一臺(tái)機(jī)器上。

kube-scheduler、kube-controller-manager 和 kube-apiserver 三者的功能緊密相關(guān)；
同時(shí)只能有一個(gè) kube-scheduler、kube-controller-manager 進(jìn)程處于工作狀態(tài)，如果運(yùn)行多個(gè)，則需要通過(guò)選舉產(chǎn)生一個(gè) leader；

安裝

wget https://dl.k8s.io/v1.6.2/kubernetes-server-linux-amd64.tar.gz
tar -xzvf kubernetes-server-linux-amd64.tar.gz
cp -r kubernetes/server/bin/{kube-apiserver,kube-controller-manager,kube-scheduler,kubectl,kube-proxy,kubelet} /usr/bin/

配置和啟動(dòng) kube-apiserver

創(chuàng)建 kube-apiserver的service配置文件
/usr/lib/systemd/system/kube-apiserver.service內(nèi)容：

[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

/etc/kubernetes/config文件的內(nèi)容為：

# 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://sz-pg-oam-docker-test-001.tendcloud.com:8080"
KUBE_MASTER="--master=http://192.168.100.17:8080"

apiserver配置文件/etc/kubernetes/apiserver內(nèi)容為：

###
## 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="--insecure-bind-address=sz-pg-oam-docker-test-001.tendcloud.com"
KUBE_API_ADDRESS="--advertise-address=192.168.100.17 --bind-address=192.168.100.17 --insecure-bind-address=192.168.100.17"
#
## 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://192.168.100.17:2379,192.168.100.19: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=3 --audit-log-maxage=30 --audit-log-maxbackup=3 --audit-log-maxsize=100 --audit-log-path=/var/lib/audit.log --event-ttl=1h"
  • --authorization-mode=RBAC 指定在安全端口使用 RBAC 授權(quán)模式，拒絕未通過(guò)授權(quán)的請(qǐng)求；
  • kube-scheduler、kube-controller-manager 一般和 kube-apiserver 部署在同一臺(tái)機(jī)器上，它們使用非安全端口和 kube-apiserver通信;
  • kubelet、kube-proxy、kubectl 部署在其它 Node 節(jié)點(diǎn)上，如果通過(guò)安全端口訪(fǎng)問(wèn) kube-apiserver，則必須先通過(guò) TLS 證書(shū)認(rèn)證，再通過(guò) RBAC 授權(quán)；
  • kube-proxy、kubectl 通過(guò)在使用的證書(shū)里指定相關(guān)的 User、Group 來(lái)達(dá)到通過(guò) RBAC 授權(quán)的目的；
  • 如果使用了 kubelet TLS Boostrap 機(jī)制，則不能再指定 --kubelet-certificate-authority、--kubelet-client-certificate 和 --kubelet-client-key 選項(xiàng)，否則后續(xù) kube-apiserver 校驗(yàn) kubelet 證書(shū)時(shí)出現(xiàn) ”x509: certificate signed by unknown authority“ 錯(cuò)誤；
  • --admission-control 值必須包含 ServiceAccount；
  • --bind-address 不能為 127.0.0.1；
  • runtime-config配置rbac.authorization.k8s.io/v1beta1，表示運(yùn)行時(shí)的apiVersion；
  • --service-cluster-ip-range 指定 Service Cluster IP 地址段，該地址段不能路由可達(dá)；
  • 缺省情況下 kubernetes 對(duì)象保存在 etcd /registry 路徑下，可以通過(guò) --etcd-prefix 參數(shù)進(jìn)行調(diào)整；

啟動(dòng) kube-apiserver

systemctl daemon-reload
systemctl enable kube-apiserver
systemctl start kube-apiserver

配置和啟動(dòng) kube-controller-manager

創(chuàng)建 kube-controller-manager的serivce配置文件

文件路徑/usr/lib/systemd/system/kube-controller-manager.service

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

配置文件/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"
  • --service-cluster-ip-range 參數(shù)指定 Cluster 中 Service 的CIDR范圍，該網(wǎng)絡(luò)在各 Node 間必須路由不可達(dá)，必須和 kube-apiserver 中的參數(shù)一致；
  • --cluster-signing-* 指定的證書(shū)和私鑰文件用來(lái)簽名為 TLS BootStrap 創(chuàng)建的證書(shū)和私鑰；
  • --root-ca-file 用來(lái)對(duì) kube-apiserver 證書(shū)進(jìn)行校驗(yàn)，指定該參數(shù)后，才會(huì)在Pod 容器的 ServiceAccount 中放置該 CA 證書(shū)文件；
  • --address 值必須為 127.0.0.1，因?yàn)楫?dāng)前 kube-apiserver 期望 scheduler 和 controller-manager 在同一臺(tái)機(jī)器

啟動(dòng) kube-controller-manager

systemctl daemon-reload
systemctl enable kube-controller-manager
systemctl start kube-controller-manager

配置和啟動(dòng) kube-scheduler

創(chuàng)建 kube-scheduler的service配置文件

文件路徑/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

配置文件/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"

啟動(dòng) kube-scheduler

systemctl daemon-reload
systemctl enable kube-scheduler
systemctl start kube-scheduler

查看組件狀態(tài)

kubectl get componentstatuses
最后編輯于 ：
?著作權(quán)歸作者所有,轉(zhuǎn)載或內(nèi)容合作請(qǐng)聯(lián)系作者
【社區(qū)內(nèi)容提示】社區(qū)部分內(nèi)容疑似由AI輔助生成，瀏覽時(shí)請(qǐng)結(jié)合常識(shí)與多方信息審慎甄別。
平臺(tái)聲明：文章內(nèi)容（如有圖片或視頻亦包括在內(nèi)）由作者上傳并發(fā)布，文章內(nèi)容僅代表作者本人觀點(diǎn)，簡(jiǎn)書(shū)系信息發(fā)布平臺(tái)，僅提供信息存儲(chǔ)服務(wù)。

相關(guān)閱讀更多精彩內(nèi)容

友情鏈接更多精彩內(nèi)容