[OCCM] Shared Loadbalancer behavior

[modzilla99]

Hey,

based on #2190 and #2174 the behavior of shared Loadbalancers were refactored. It is no longer possible to share internal Loadbalancer services. Since we rely on this behavior and let 2 services share a single LoadBalancer I'd like an option to reenable this feature.

One idea I have is that we prevent other "child" services to attach a FIP to the LoadBalancer and print a warning event explaining the situation. That way only owner of the service manages it's state, which would be acceptable to me. If that is too risky, we could add an annotation to "allow the risk".

Best regards,
Justin Lamp

[Mistikan]

Hello. I agree with @modzilla99.

I use service.beta.kubernetes.io/openstack-internal-load-balancer: "true" for ingress forwarding and would like to have DNS ports (TCP/UDP) forwarded on the same IP.

Links:

• https://docs.selectel.ru/en/cloud/managed-kubernetes/networks/set-up-ingress/ -> "With load balancer configuration" -> "Manifest fragment with block annotations".