There are some brief ideas you should understand about building a multiple-master system:
- Add a load balancer server in front of the masters. The load balancer will become the new endpoint accessed by nodes and clients.
- Every master runs its own API server.
- Only one scheduler and one controller manager are eligible to work in the system, which can avoid conflicting directions from different daemons while managing containers. To achieve this setup, we enable the --leader-elect flag in the scheduler and controller manager. Only the one getting the lease can take duties.
In this recipe, we are going to build a two-master system via kubeadm, which has similar methods while scaling more masters. Users may also use other tools to ...