kubernetes / kubernetes/cloud-provider-openstack
[occm] octavia loadbalancer with native pod routing
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 720
- Forks
- 687
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 51
Description
/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 nod IPs with 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:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the Octavia load-balancer path for Services with AllocateLoadBalancerNodePorts=false and compare it with the existing node IP and nodePort member behavior. Done means native pod routing creates Octavia members using pod IPs, with coverage for the reproduction described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- cloud, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100