metallb.universe.tf/allow-shared-ip doesn't work

706 views
Skip to first unread message

Oren Zipori

unread,
Nov 22, 2020, 2:40:29 PM11/22/20
to metallb-users
Hi
I setup MetalLB for my RPI 4 cluster, I'm running metallb/controller:v0.9.5 using the manifest installation from the MetalLB installation page.
I'm trying to set my pihole to use metallb so i can run both UDP and TCP services on the same IP Address, But when the 2 services are created only one get the shared IP and the other is stuck at pending with this error:

failed to allocate IP for "pihole/pihole-tcp": can't change sharing key for "pihole/pihole-tcp", address also in use by pihole/pihole-udp

Does anyone know what cloud be the issue? from what I understand it supposes to work without any issues.

Rodrigo Campos

unread,
Dec 7, 2020, 9:49:17 AM12/7/20
to Oren Zipori, metallb-users
You probably created the sharing key after a service already had the
IP allocated. Can you please try, for example, to delete the k8s
services and create them from scratch with the annotation?
> --
> You received this message because you are subscribed to the Google Groups "metallb-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to metallb-user...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/metallb-users/752cf280-efea-4f76-8c84-4cdb347362c9n%40googlegroups.com.



--
Rodrigo Campos
---
Kinvolk GmbH | Adalbertstr.6a, 10999 Berlin | tel: +491755589364
Geschäftsführer/Directors: Alban Crequy, Chris Kühl, Iago López Galeiras
Registergericht/Court of registration: Amtsgericht Charlottenburg
Registernummer/Registration number: HRB 171414 B
Ust-ID-Nummer/VAT ID number: DE302207000

Oren Zipori

unread,
Dec 12, 2020, 1:33:19 PM12/12/20
to metallb-users
My issue was resolved by adding to the service resource the annotation of: externalTrafficPolicy: Local 
This with the edition of the metallb.universe.tf/allow-shared-ip: pihole enable my two services to run on the same IP. I don't understand why the externalTrafficPolicy fixed it but it did.

Cheers

Reply all
Reply to author
Forward
0 new messages