Hide Forgot
Description of problem: OVN native L4LB for east-west traffic ------------------------------------- Kuryr implements clusterIP (east-west traffic) services not by using iptables redirect clauses (kube-proxy) but using amphora driver backed Octavia Load balancers. This has an evidently high cost in memory/core resources as well as it adds extra hops that deteriorate the data plane performance (pod -> router -> LB amphora -> router -> service pod). This feature is about optionally replacing the clusterIP services backing with OVN’s native load balancers (only TCP traffic). This would have the communication be directly pod -> service pod since OVN’s L4 load balancer is distributed just like its router. This would not apply to load balancer service types. Additional info:
Adding related upstream patch sets
This will also depend on the fix for these two: - https://bugs.launchpad.net/networking-ovn/+bug/1794260 - https://storyboard.openstack.org/#!/story/2003833
Checked with 4.4.0-0.nightly-2020-01-24-045907 Ran kuryr_tempest_plugin.tests.scenario.test_service.TestServiceScenario.test_pod_service_curl and verified that the LB of the service is using ovn as a backend
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0581