If you want the kubernetes master isolation.
Kubernetes Master Isolation does not allow PODs to be scheduled on the master. This is when the masters and the nodes have been identically configured to potentially allow scheduling of PODs on them by kubernetes. And you plan that the masters should not be allowed to schedule the PODs created by kubernetes to be run on them.
The below removes the taint so as the PODs can be scheduled on the master as well.
kubectl taint nodes --all node-role.kubernetes.io/master-
Remove the taints on the master so that you can schedule pods on it.
kubectl taint nodes --all node-role.kubernetes.io/master-
It should return the following.
node "<your-hostname>" untainted
Confirm that you now have a node in your cluster with the following command.
kubectl get nodes
Installation of Heapster and Kibana or similar tools
To be done later.
Other relevant links for this documentation.
You can click on any of the link to view them.
The Main Document - Kubernetes 1.10.0 with 3 Master and Slave nodes and SSL on CentOS7
KVM Host and Guest Preprations
SSL Certificate Generations
Configure simple external HAPROXY
Configuring ETCD with SSL on the Master servers
Creation of the POD Network information in ETCD for flanneld
Install and Configure the Master Service on the Kubernetes Master servers
Installation and Configuration of the Kubernetes Slaves
Installation and testing of kube-dns
You can click on any of the link to view them.
The Main Document - Kubernetes 1.10.0 with 3 Master and Slave nodes and SSL on CentOS7
KVM Host and Guest Preprations
SSL Certificate Generations
Configure simple external HAPROXY
Configuring ETCD with SSL on the Master servers
Creation of the POD Network information in ETCD for flanneld
Install and Configure the Master Service on the Kubernetes Master servers
Installation and Configuration of the Kubernetes Slaves
Installation and testing of kube-dns
