MetalLB - how to troubleshoot - no availble IPs

### Cluster information:

Kubernetes version: **1.18.2**
Cloud being used: **Bare-Metal**
Installation method: **Ansible -**
Host OS: **Debian 10**
CNI and version: **Calico - v3.8.8-1**
CRI and version: Docker - **19.03.8, build afacb8b7f0**


I’m trying to get MetalLB to work with my setup.
pfSense: OpenBGBD enabled and status says it sending messages to the workers.

I have two VLANs one for Kubernetes and one for MetalLB deployments:

  • - Kuberentes net
  • - MetalLB net

I am running OpenBGBD on a virtual router IP adress:
I can reach port 179/tcp from my workers so no FW issue from what I can gather.

My MetalLB config:

apiVersion: v1
kind: ConfigMap
  namespace: metallb-system
  name: config
  config: |
    - my-asn: 64513
      peer-asn: 64512
    - name: my-ip-space
      protocol: bgp

The logs say:
{"caller":"service.go:90","error":"no available IPs","msg":"IP allocation failed","op":"allocateIP","service":

Now the workers only have one network card and that is connected to the net. Is that correct or should I be adding a 2nd network adapter and connect it to the net as well?