Currently, the various endpoints needed per hostedcluster are exposed through a combination of LoadBalancers and routes. The LoadBalancer is mostly needed because we can not do name-based virtual hosting for the KAS, as all in-cluster traffic uses the kubernetes.default hostname, making it impossible to find out which cluster the traffic belongs to.

We started to manage our own router for the private cluster case. Since this router is per hostedcluster, we can use it for the KAS as well. In order to simplify things, make traffic accounting possible and save on LoadBalancers, it would be good if we used this router for all traffic.

AC:

• The per-hostedcluster router is always created, not only in the private case
• All hostedcluster endpoints (KAS, konnektivity, ovnkube, ignition...) are exposed through this router
• The change is backwards compatible, existing cluster that use a kas LB need to remain that way
• DNS entries are configured through route annotations and will be managed by the external DNS operator