If amphora lb-provider is configured on the OCP cluster and the customer wants to use a loadbalancer service with lb-method different to ROUND_ROBIN (LEAST_CONNECTIONS, or SOURCE_IP), it is mandatory to configure "create-monitor=true" on  cloud-provider-config and ETP:Local on the service to get it working.

If not, regardless the SOURCE_IP or LEAST_CONNECTIONS method is shown on the Amphora loadbalancer attributes, kubeproxy is at the end doing ROUND_ROBIN so the customer experience is that the lb-method is not being applied. Monitors and ETP:Local helps to avoid this effect.

4.12

U/S documentation: https://github.com/kubernetes/cloud-provider-openstack/blob/master/docs/openstack-cloud-controller-manager/using-openstack-cloud-controller-manager.md#load-balancer