phillyfere.blogg.se

1. #Install kubernetes cluster multi master install#
2. #Install kubernetes cluster multi master download#

Download the latest “requests” package (.tar.gz file) Note: While installing all requirements packages, if you get errors related to “requests” package, follow the steps below: (Install dependencies from requirements.txt) ~]# cd kubespray

#Install kubernetes cluster multi master install#

In the example below, we will be installing a 5 server cluster (3 as Master & all 5 as nodes)ĥ. Git clone the Kubespray repository on one of the master servers: ~]# git clone Ħ. Go to the ‘Kubespray’ directory and install all dependency packages Now let’s start with Kubespray activities. So at this stage all the preparation work is completed. If possible, you can stop firewall service on all servers in the cluster: ~]# systemctl stop firewalldģ. Install some prerequisites packages on all servers in the clusterĪnsible: ~]# sudo yum install epel-releaseĤ. Enable passwordless login between all servers in the cluster. ~]# firewall-cmd -permanent -add-port=6783/tcp On all “node” servers: ~]# firewall-cmd -permanent -add-port=10250/tcp ~]# echo '1' > /proc/sys/net/bridge/bridge-nf-call-iptables ~]# firewall-cmd -permanent -add-port=10255/tcp ~]# firewall-cmd -permanent -add-port=10252/tcp ~]# firewall-cmd -permanent -add-port=10251/tcp ~]# firewall-cmd -permanent -add-port=10250/tcp Set the firewall rules on all “master” Servers: ~]# firewall-cmd -permanent -add-port=6443/tcp

~]# sed -i -follow-symlinks 's/SELINUX=enforcing/SELINUX=disabled/g' /etc/sysconfig/selinuxĢ. Perform the following steps on all servers that need to be added in cluster: The official Kubespray GitHub link is here, but the installation steps mentioned are very minimal. Kubespray gives a simple and easy way to install a multi-master, production-ready HA cluster for deploying any business-critical applications. So the need for HA of master nodes arrives to mitigate this scenario. While deploying K8s on production environments it’s a common observation that the master node becomes a single point of failure, and any business-critical production environments can’t afford to have that. So the assumption will be that you are already good with basics of K8S and are now looking for some real implementation stuff. If you are on this page and reading along, that means you are a Kubernetes enthusiast and have already tried your hand with Kubernetes.