OCCM support use service endpoint ip as loadbalancer member. #3033
Description
/kind feature
What happened:
We have applied F5 + route-reflector as openstack load balancing solution
route-reflector has granted us ability to brodcast pod id inside the newtwork, so instead of using node port we'd prefer to have pod ip as the as loadbalancer backend member.
What you expected to happen:
For type: loadbalancer service, OCCM support use service endpoint ip as loadbalancer member.
How to reproduce it:
NA
Anything else we need to know?:
NA
Environment:
- openstack-cloud-controller-manager(or other related binary) version: v1.34.1
- OpenStack version:
- Others: