Open
Description
The metallb of our Kubernetes cluster throws that error on startup:
{"branch":"HEAD","caller":"level.go:63","commit":"v0.12.1","goversion":"gc / go1.16.14 / amd64","level":"info","msg":"MetalLB controller starting version 0.12.1 (commit v0.12.1, branch HEAD)","ts":"2023-07-17T07:11:16.64900186Z","version":"0.12.1"}
{"caller":"level.go:63","configmap":"metallb-system/config","error":"peer #25 already exists","event":"configStale","level":"error","msg":"config (re)load failed, config marked stale","ts":"2023-07-17T07:11:24.348221116Z"}
{"caller":"level.go:63","event":"stateSynced","level":"info","msg":"controller synced, can allocate IPs now","ts":"2023-07-17T07:11:24.448924397Z"}
the respective peer config is:
- hold-time: ""
my-asn: xxxx
node-selectors:
- match-expressions: []
match-labels:
kubernetes.io/hostname: shoot--codesphere--fra-worker-67fdf-m76pk
- match-expressions: null
match-labels:
nomatch.metal.equinix.com/service-name: prerequisites-ingress-nginx-controller
nomatch.metal.equinix.com/service-namespace: default
- match-expressions: null
match-labels:
nomatch.metal.equinix.com/service-name: workspace-reverse-proxy-ingress-nginx-controller
nomatch.metal.equinix.com/service-namespace: default
password: ""
peer-address: 169.254.255.1
peer-asn: xxxx
peer-port: 0
router-id: ""
source-address: ""
In the equinix metalconsole I also see that we 2 nodes without a learned bgp route (might be related).
Environment:
K8s: 1.22.17
Equinix CCM: v3.6.2
MetalLb: 0.12.1