Metallb bundle port in use

[jarred wilson]

The juju bundle published at containers-metallb has metallb-controller and metallb-speaker using the same port. There is no port configuration option for these charms.

$ juju status | grep 7472
metallb-controller/0* active idle 10.1.88.80 7472/TCP
metallb-speaker/0* blocked idle 7472/TCP 0/1 nodes are available: 1 node(s) didn't have free ports for the requested pod ports.

[jarred wilson (jardon)]

To add more detail here:

applications:
  metallb-speaker:
    charm: cs:~containers/metallb-speaker-19
    series: kubernetes
    os: kubernetes
    charm-origin: charmstore
    charm-name: metallb-speaker
    charm-rev: 19
    charm-channel: stable
    scale: 1
    provider-id: 25648d10-60a5-4ab3-a35a-ea452dad9922
    address: 10.152.183.15
    exposed: false
    application-status:
      current: waiting
      since: 05 Apr 2022 16:40:40Z
    units:
      metallb-speaker/0:
        workload-status:
          current: blocked
          message: '0/1 nodes are available: 1 node(s) didn''t have free ports for the requested pod ports.'
          since: 05 Apr 2022 16:40:40Z
        juju-status:
          current: idle
          since: 05 Apr 2022 16:40:47Z
        leader: true
        open-ports:
        - 7472/TCP
        provider-id: 252aaab3-d1db-45c4-9265-73c5c6c95dba
    version: registry.jujucharms.com/containers/metallb-speaker/metallb-speaker-image@sha256:db0ebd9b3ef47881ed50d9bc036b65306f4ddbe8f0cf781b89b96cd881ce79b3
  metallb-controller:
    charm: cs:~containers/metallb-controller-20
    series: kubernetes
    os: kubernetes
    charm-origin: charmstore
    charm-name: metallb-controller
    charm-rev: 20
    charm-channel: stable
    scale: 1
    provider-id: 312603fa-0d30-47a5-a141-c69b26d082e8
    address: 10.152.183.107
    exposed: false
    application-status:
      current: active
      since: 05 Apr 2022 16:40:48Z
    units:
      metallb-controller/0:
        workload-status:
          current: active
          since: 05 Apr 2022 16:40:31Z
        juju-status:
          current: idle
          since: 05 Apr 2022 16:40:48Z
        leader: true
        open-ports:
        - 7472/TCP
        address: 10.1.88.80
        provider-id: bba000c2-df1e-4bff-8cd8-53e4672533e3
    version: registry.jujucharms.com/containers/metallb-controller/metallb-controller-image@sha256:c8b0da00dd83db99bf00fb7088c33e7aaf52fa679f962610f1fe5ed173f66b77

[Adam Dyess (addyess)]

I believe that port 7472 is used as a port for opening for metrics scraping.

I can see that it is apart of the upstream manifests:

```
      annotations:
        prometheus.io/port: "7472"
        prometheus.io/scrape: "true"
```

It could be possible in future releases to close this port or reassign the prometheus metrics port with charm configuration. I'll leave this bug as triaged marked for a future release.

[Adam Dyess (addyess)]

It's unclear this still applies as using the 2 charm solution is no longer advised. I think we should parking lot this bug now that metallb is a single charm.