Context

We'll need to implement support for MetalLB's CRD-based configuration, in order to be able to update to MetalLB >= 0.13.2. From the release notes:

CRD support! A long awaited feature, MetalLB is now configurable via CRs. On top of that, validating webhooks will ensure the validity of the configuration upfront, without needing to check the logs. (PR #1237, PR #1245) Please note that the ConfigMap configuration is not supported anymore. Check the “Changes in behaviour” section for more details.

I've implemented the bare minimum required for Layer2 mode (including forward migrations from the old config parameters), cf. #38. However, we'll need to also implement support for the BGP mode CRs. See https://metallb.universe.tf/configuration/ for all the CRs we'll need to support.

Design-wise, we'll have to decide if we want any logic, or if we just want to expose the CRs in the hierarchy directly.

Alternatives

n/a, We have to do this to upgrade to >= 0.13.2.

The component sometimes fails to compile if it is compiled with different Helm chart versions in the same working directory without deleting dependencies/metallb/helmcharts between runs

Steps to Reproduce the Problem

1. Compile component with different Helm chart versions in same working directory without deleting dependencies/metallb/helmcharts between compilations

Actual Behavior

Helm error:

Error: values don't meet the specifications of the schema(s) in the following chart(s):
metallb:
- speaker: tolerateMaster is required
- speaker: Must validate all the schemas (allOf)
- prometheus: podMonitor is required
- prometheus.prometheusRule: staleConfig is required
- prometheus.prometheusRule: configNotLoaded is required
- prometheus.prometheusRule: addressPoolExhausted is required
- prometheus.prometheusRule: addressPoolUsage is required
- prometheus.prometheusRule: bgpSessionDown is required

Expected Behavior

Component compiles regardless of Chart version changes without manually deleting dependencies