Asking for help? Comment out what you need so we can get more information to help you!
Microk8s cluster beside a separate load balancer NGINX. Need to create a single kube config file to balance API traffic. So regarding the Nginx loadbalancer for HA Setup - We’ll need to loadbalance traffic on the nginx ingress controllers and the k8s API traffic should also go through the nginx Loadbalancer (Using TCP loadbalancing). We will need to look at on generating a single kubeConfig file (Probably using the LB IP?? ) if possible so when somebody runs ‘kubectl’ commands, the API traffic will go through Nginx LB into the respective registered k8s API / control plane nodes. Nginx can act as a TCP loadbalancer as well (Can achieve the same behavior as an AWS CLB
RE Load balancer for Remote HA - We have several options - However yes the customer would probably need to have a software/hardware loadbalancer (The loadbalancer might need to support HTTP &/or TCP loadbalancing algorithms) as since we have multiple nodes (In the case of microk8s HA, the control plane also runs in multiple nodes). The loadbalancer is needed to communicate with the HA k8s API server and also the Nginx controller (It is likely to run as a k8s daemonSet rather than a deployment)
Cluster information:
Kubernetes version: 1.21.9
Cloud being used: (put bare-metal if not on a public cloud) VM bare metal
Installation method: manual
Host OS: Ubuntu 20.4
CNI and version:
CRI and version:
You can format your yaml by highlighting it and pressing Ctrl-Shift-C, it will make your output easier to read.