The difficulty with this is that if you have 2 api-loadbalancers, you then need something in front of those so that you have one ingress point to the cluster. There are several options for this which are enumerated here: https://ubuntu.com/kubernetes/docs/high-availability
Which of these options to use depends on where the cluster is being deployed. This means we can't really make a one-size-fits-all bundle. This is why the default bundle today simply has one kube-api-loadbalancer. It's left up to the person deploying to choose the HA solution that works for them, and scale the components as required.
The difficulty with this is that if you have 2 api-loadbalancers, you then need something in front of those so that you have one ingress point to the cluster. There are several options for this which are enumerated here: https:/ /ubuntu. com/kubernetes/ docs/high- availability
Which of these options to use depends on where the cluster is being deployed. This means we can't really make a one-size-fits-all bundle. This is why the default bundle today simply has one kube-api- loadbalancer. It's left up to the person deploying to choose the HA solution that works for them, and scale the components as required.