Bug 2050869 - Two features required for customer to successfully implement MetalLB in their environment
Summary: Two features required for customer to successfully implement MetalLB in their...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.9
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: 4.10.0
Assignee: Mohamed Mahmoud
QA Contact: Arti Sood
URL:
Whiteboard:
Depends On:
Blocks: 2052549
TreeView+ depends on / blocked
 
Reported: 2022-02-04 19:53 UTC by emacdona
Modified: 2022-02-17 20:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-02-09 21:49:59 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift metallb-operator pull 61 0 None open Bug 2050869: MetalLB CR: add speaker pods Tolerations support 2022-02-07 18:33:20 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.