Skip to content

metallb: Use CNO as the integration point #721

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
russellb wants to merge 1 commit into from
Closed

metallb: Use CNO as the integration point #721

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
39 changes: 10 additions & 29 deletions enhancements/network/on-prem-service-load-balancers.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -229,35 +229,16 @@ doing all of your testing in a virtual network built on top of it.

#### Operator

This is the first of two alternatives for how we might integrate MetalLB in
OpenShift.

We must also create an operator for MetalLB. We should develop an operator
that is generally useful to the MetalLB community. We should also have an
OpenShift version of this operator for our use.

It is assumed that the MetalLB operator would be managed by OLM as an optional
additional component to be installed on on-premise clusters. However, in the
[ROADMAP.md
document](https://github.com/openshift/enhancements/blob/master/ROADMAP.md),
there is an item to "Front the API servers and other master services with
service load balancers". If this functionality is required at install time,
the details on management of this operator may be revisited.

There is a start of a
[metallb-operator](https://github.com/cybertron/metallb-operator) available and
a [video demo](https://www.youtube.com/watch?v=WgOZno0D7nw).

#### Alternative Integration: Cloud Controller Manager

An alternative integration approach would be via a cloud controller manager
(CCM). An example of this is the [packet.net
CCM](https://github.com/packethost/packet-ccm), which ensures MetalLB is
deployed and also configures it properly to work in packet.net’s BGP
environment.

These integration options must be explored in more detail as part of a more
detailed integration proposal.
CRDs for the configuration of MetalLB will be done as part of the main MetalLB
project. We will use the Cluster Network Operator (CNO) for managing the
deployment of MetalLB on OpenShift. It's possible that we will want to have
MetalLB on by default for bare metal or other on-premise infrastructure
clusters in the future, and using the CNO will give us this flexibility.

At this time, we do not expect any new configuration required for the CNO. The
expectation is to deploy MetalLB automatically if we see an instance of a
MetalLB configuration resource get created, and we're on a platform where we
allow MetalLB to be used, which would be bare metal only to start.

### Risks and Mitigations

Expand Down