-
Feature
-
Resolution: Done
-
Normal
-
None
Feature Overview (aka. Goal Summary)
To bring feature parity to ppc64le and s390x with x86 for the MetalLB Operator
Acceptance Criteria
The scenarios documented above work as expected on ppc64le
The scenarios documented above work as expected on s390x
Goals (aka. expected user outcomes)
IBM Power and IBM zSystem customers can make use of the MetalLB operator
Requirements (aka. Acceptance Criteria):
Scenarios from existing OCP 4.11 docs for x86 are available on Power and zSystems:
1. https://docs.openshift.com/container-platform/4.11/networking/metallb/about-metallb.html
2. https://docs.openshift.com/container-platform/4.11/networking/metallb/metallb-operator-install.html
Use Cases (Optional):
Include use case diagrams, main success scenarios, alternative flow scenarios. Initial completion during Refinement status.
Questions to Answer (Optional):
Include a list of refinement / architectural questions that may need to be answered before coding can begin. Initial completion during Refinement status.
Out of Scope
High-level list of items that are out of scope. Initial completion during Refinement status.
Background
Provide any additional context is needed to frame the feature. Initial completion during Refinement status.
Customer Considerations
Provide any additional customer-specific considerations that must be made when designing and delivering the Feature. Initial completion during Refinement status.
Documentation Considerations
Provide information that needs to be considered and planned so that documentation will meet customer needs. Initial completion during Refinement status.
Interoperability Considerations
Which other projects and versions in our portfolio does this feature impact? What interoperability test scenarios should be factored by the layered products? Initial completion during Refinement status.