In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-01-16 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Servers >
Share
Shulou(Shulou.com)06/03 Report--
Follow up with a single-node deployment (1) deploy a multi-node deployment environment
Load balancing
Nginx1:192.168.13.128/24
Nginx2:192.168.13.129/24
Master node
Master1:192.168.13.131/24 kube-apiserver kube-controller-manager kube-scheduler etcd
Master2:192.168.13.130/24 kube-apiserver kube-controller-manager kube-scheduler etcd
Node node
Node1:192.168.13.132/24 kubelet kube-proxy docker flannel etcd
Node2:192.168.13.133/24 kubelet kube-proxy docker flannel etcd
Deployment of master02 1, close the master02 firewall [root@master02 ~] # systemctl stop firewalld.service [root@master02 ~] # setenforce 02, and copy the kubernetes directory from master01 Component server service to Master02 [root @ master01 K8s] # scp-r / opt/kubernetes/ root@192.168.13.130:/opt## copy kubernetes directory to Master02 [root @ master01 K8s] # scp / usr/lib/systemd/system/ {kube-apiserver,kube-controller-manager,kube-scheduler} .service root@192.168.13.130:/usr/lib/systemd/system/## copy the three components startup script 3 in master Modify the configuration file in master02 [root@master02 ~] # cd / opt/kubernetes/cfg/ [root@master02 cfg] # vim kube-apiserve # # modify the apiserver configuration file-- bind-address=192.168.13.130\ # # modify the address-- secure-port=6443\-- advertise-address=192.168.13.130\ # # modify address 4, copy the existing etcd certificate on master01 for master02 use (master02 must have etcd certificate Otherwise, the apiserver service cannot be started) [root@master01 k8s] # scp-r / opt/etcd/ root@192.168.13.130:/opt/## operate in master02 [root@master02 cfg] # systemctl start kube-apiserver.service # # start the service [root@master02 cfg] # systemctl enable kube-apiserver.service [root@master02 cfg] # systemctl start kube-controller-manager.service [root@master02 cfg] # systemctl enable kube-controller-manager.service [root@master02 cfg] # systemctl Start kube-scheduler.service [root@master02 cfg] # systemctl enable kube-scheduler.service5 Modify environment variable [root@master02 cfg] # vim / etc/profileexport PATH=$PATH:/opt/kubernetes/bin/ # # add environment variable [root@master02 cfg] # source / etc/profile # # Refresh configuration file [root@master02 cfg] # kubectl get node # # View cluster node information NAME STATUS ROLES AGE VERSION192.168.13.132 Ready 75m v1.12.3192.168.13.133 Ready 55m v1.12.3 Multi-master node deployment completed To be continued.
Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.