Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to configure Control Plane Load Balancer #4386

Open
zerowebcorp opened this issue Jan 29, 2024 · 2 comments
Open

How to configure Control Plane Load Balancer #4386

zerowebcorp opened this issue Jan 29, 2024 · 2 comments
Labels
inactive kind/support Question with a workaround

Comments

@zerowebcorp
Copy link

Hello, I've checked the documentation on how to setup ha with microk8s. However I am not finding anything that explains the additional steps to do in order to put a load balancer ( I am using an azure load balancer) in front of the 3 VMs where microk8s is installed on HA mode so that I when I run microk8s add-node I get the IP address of the load balancer instead of the node's ip where I executed the command so that the worker nodes use it to connect to one of the 3 manager nodes.

@neoaggelos
Copy link
Contributor

Hi @zerowebcorp, pasting my response from a similar Slack thread this week:

Using a LoadBalancer service for the control plane is a chicken-egg problem, therefore it is typically not recommended

Most often, you need to setup a load balancer that proxies requests to the control plane nodes. The way to do this varies by cloud. The common step is to make sure that the loadbalancer IP or DNS is added as a SAN in the kube-apiserver certificates (see https://microk8s.io/docs/services-and-ports) for details.

Solutions include:

  • using a virtual IP across the nodes (by means of keepalived or kube-vip)
  • using an external load balancer provided by the cloud (e.g. Elastic LoadBalancer on AWS, octavia on openstack, etc)

@neoaggelos neoaggelos added the kind/support Question with a workaround label Feb 1, 2024
Copy link

stale bot commented Dec 27, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the inactive label Dec 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
inactive kind/support Question with a workaround
Projects
None yet
Development

No branches or pull requests

2 participants