/kind feature
What happened:
Creating a Loadbalancer service with AllocateLoadBalancerNodePorts=false won't add any members to the octavia LB. this was implemented on purpose as far as I can see here
What you expected to happen:
We are using native pod routing in the k8s cluster with --configure-cloud-routes=true feature, so the pod IP's are reachable within the vlan segment. The octavia instances being in the same vlan segment, could reach the pod IP's without an additional hop (nodeport).
Create members in octavia with pod IP's instead of nodeport.
How to reproduce it:
Create a Loadbalancer service with AllocateLoadBalancerNodePorts=false.
Anything else we need to know?:
Environment:
- openstack-cloud-controller-manager(or other related binary) version: 1.34.1
- OpenStack version:
- Others:
/kind feature
What happened:
Creating a Loadbalancer service with
AllocateLoadBalancerNodePorts=falsewon't add any members to the octavia LB. this was implemented on purpose as far as I can see hereWhat you expected to happen:
We are using native pod routing in the k8s cluster with
--configure-cloud-routes=truefeature, so the pod IP's are reachable within the vlan segment. The octavia instances being in the same vlan segment, could reach the pod IP's without an additional hop (nodeport).Create members in octavia with pod IP's instead of nodeport.
How to reproduce it:
Create a Loadbalancer service with
AllocateLoadBalancerNodePorts=false.Anything else we need to know?:
Environment: