During The MetalLB Version Upgrade To 0.13.7, Service IPs From Custom IPAddressPools [2nd] Getting Re-assgined.
Problem
During the MetalLB upgrade from 0.10.2 to 0.13.7, it is observed that the External IP of the services in the ipaddresspool other than the default IPAddressPools were changed during this upgrade process.
Here is a sample of before and after the change for some of these services:
x
-service-1 service1 LoadBalancer 10.21.66.75 10.32.209.8 19000:32239/TCP 189d+service-1 service1 LoadBalancer 10.21.66.75 10.32.209.14 19000:32239/TCP 189d-service-2 service2 LoadBalancer 10.21.57.98 10.32.209.12 19010:31598/TCP 106d+service-2 service2 LoadBalancer 10.21.57.98 10.32.209.15 19010:31598/TCP 106dEnvironment
- Platform9 Managed Kubernetes - v-5.6 and Higher.
Answer
The issue is resolved in the PMK-5.10.2 release.
Additional Information
The jira used to track the the issue is PMK-6161.
Was this page helpful?