-
Feature
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
BU Product Work
-
False
-
-
False
-
50% To Do, 50% In Progress, 0% Done
-
0
-
Program Call
Feature Overview (aka. Goal Summary)
Support the balance-slb bond mode from OVS.
Goals (aka. expected user outcomes)
Support a loadbalanced bond mode that does not require configuration on the switch, and specifically the balance-slb mode from OVS that can be approximated with balance-xor in non-OVS bonds.
Requirements (aka. Acceptance Criteria):
Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed. Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.
Deployment considerations | List applicable specific needs (N/A = not applicable) |
Self-managed, managed, or both | |
Classic (standalone cluster) | |
Hosted control planes | |
Multi node, Compact (three node), or Single node (SNO), or all | |
Connected / Restricted Network | |
Architectures, e.g. x86_x64, ARM (aarch64), IBM Power (ppc64le), and IBM Z (s390x) | |
Operator compatibility | |
Backport needed (list applicable versions) | |
UI need (e.g. OpenShift Console, dynamic plugin, OCM) | |
Other (please specify) |
Use Cases (Optional):
- Support an often-used load balancing functionality in OVN-Kubernetes that customers migrating from legacy virtualization platforms require for an easy transition.
Questions to Answer (Optional):
Out of Scope:
Background
Customer Considerations
Documentation Considerations
Interoperability Considerations