Using an Existing Load Balancer in Kubernetes

Currently, when creating a service of type LoadBalancer in a managed Kubernetes cluster, a new load balancer is automatically provisioned in Gcore. Consequently, we cannot control the IP address of this load balancer or use a single Gcore load balancer for multiple services.

It would be beneficial to have the ability to select an existing Gcore load balancer for a Kubernetes LoadBalancer service via annotations.