Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2050869

Summary: Two features required for customer to successfully implement MetalLB in their environment
Product: OpenShift Container Platform Reporter: emacdona
Component: NetworkingAssignee: Mohamed Mahmoud <mmahmoud>
Networking sub component: Metal LB QA Contact: Arti Sood <asood>
Status: CLOSED CURRENTRELEASE Docs Contact:
Severity: high    
Priority: unspecified CC: cdevaraj, ddharwar, erich
Version: 4.9   
Target Milestone: ---   
Target Release: 4.10.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-02-09 21:49:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2052549    

Description emacdona 2022-02-04 19:53:28 UTC
Description of problem: 

Two features required for customer to successfully implement MetalLB in their environment

     1. Fix introduced in version 0.11.0 of upstream MetalLB. The customer has an ingress subnet which contains only infrastructure role nodes and is separate from the worker and master role nodes. This allows different security policies to be applied in each. For MetalLB to work in an environment with multiple subnets, it requires https://github.com/metallb/metallb/pull/976.

     2. Ability to natively deploy MetalLB in "infra" nodes using nodeSelectors and tolerations. The operator must allow support to configure which nodes the pods are deployed into.

Additional info:

This requirement is a major blocker for the customer’s Beta release at the end of February.