Metallb: metalLB does not change external IP addresses after the ConfigMap update

[rifaterdemsahin]

Is this a bug report or a feature request?:
bug

What happened:
after changing config map and the restart we are still using the old addresses with the new deployments and the old ones.

What you expected to happen:
be able to get new addresses

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:
To connect https://linkedin.com/in/rifaterdemsahin/

Environment:

• MetalLB version:v0.7.3
• Kubernetes version:v1.12.2
• BGP router type/version:layer2
• OS (e.g. from /etc/os-release):ubuntu 18.04
• Kernel (e.g. uname -a):

[rifaterdemsahin]

Also pod deletion does not change the outcome

[rifaterdemsahin]

also asked the related question here in reddit
https://www.reddit.com/r/kubernetes/comments/a0kevu/cant_access_external_ip_other_than_the_kubernetes/

[danderson]

MetalLB rejects new configurations if the new configuration would break existing services. Your new configuration does not allow existing services to continue existing, so MetalLB ignored it. There are log entries in the controller and speaker pods about this.

To force MetalLB to accept an unsafe configuration, delete all the controller and speaker pods. When they restart, they'll accept the new configuration and change all your services. kubectl delete po -n metallb-system --all