Deploy KubeCF 2.6.1 Eirini with an Ingress Controller on any public cloud platform.
Check the service for eirini-ssh-proxy - it's a LoadBalancer service with an external IP.
Expected behaviour: The service in question should be a ClusterIP service as all traffic is routed through the Ingress Controller, including tcp forwarding for SSH traffic.
Impact - This does not have a functional impact but on public cloud platforms results in an unnecessary provisioning of a load balancer.
Deploy KubeCF 2.6.1 Eirini with an Ingress Controller on any public cloud platform.
Check the service for eirini-ssh-proxy - it's a
LoadBalancerservice with an external IP.Expected behaviour: The service in question should be a
ClusterIPservice as all traffic is routed through the Ingress Controller, including tcp forwarding for SSH traffic.Impact - This does not have a functional impact but on public cloud platforms results in an unnecessary provisioning of a load balancer.