The F5 IPAM Controller runs in an orchestration environment like Kubernetes to allocate IP addresses from an IPAM system to BIG-IP Virtual Servers. The purpose is to abstract complexity related to setting up BIG-IP from a networking perspective
Apache License 2.0
9
stars
16
forks
source link
IPAM breaks if ipamLabel is changed for a typeLB service #104
When I deploy an LB service with an ipamLabel that is wrong, even if I correct it later, this doesn't reflect on the service and it always shows as .
In order this to work I need to change the name of the service.
Steps To Reproduce
1) Deploy a service with an ipamLabel that doesn't exists
2) Redeploy the service with the correct label.
3) Check that the service is in pending mode.
Diagnostic Information
even if I have overwritten the IPAM label 'doesntexist', IPAM logs keep on showing this.
22/04/01 09:27:14 [DEBUG] Enqueueing on Update: kube-system/f5-cis-crd.cis-crd.ipam
2022/04/01 09:27:14 [DEBUG] Processing Key: &{0xc00045c840 0xc00045c580 Update}
2022/04/01 09:27:14 [DEBUG] [PROV] IPAM LABEL: doesntexist Not Found
2022/04/01 09:27:14 [DEBUG] Updated: kube-system/f5-cis-crd.cis-crd.ipam with Status. Removed
Hostname: Key: default/test_svc IPAMLabel: doesntexist IPAddr: Operation: Delete
2022/04/01 09:27:14 [DEBUG] Enqueueing on Update: kube-system/f5-cis-crd.cis-crd.ipam
2022/04/01 09:27:14 [DEBUG] Processing Key: &{0xc00045d340 0xc00045c840 Update}
2022/04/01 09:27:14 [DEBUG] [PROV] IPAM LABEL: doesntexist Not Found
2022/04/01 09:27:14 [DEBUG] [PROV] Unsupported IPAM LABEL: doesntexist
2022/04/01 09:27:14 [DEBUG] Enqueueing on Update: kube-system/f5-cis-crd.cis-crd.ipam
2022/04/01 09:27:14 [DEBUG] Processing Key: &{0xc0004c2000 0xc00045d340 Update}
2022/04/01 09:27:14 [DEBUG] [PROV] IPAM LABEL: doesntexist Not Found
2022/04/01 09:27:14 [DEBUG] Updated: kube-system/f5-cis-crd.cis-crd.ipam with Status. Removed
Hostname: Key: default/test_svc IPAMLabel: doesntexist IPAddr: Operation: Delete
2022/04/01 09:27:15 [DEBUG] Enqueueing on Update: kube-system/f5-cis-crd.cis-crd.ipam
2022/04/01 09:27:15 [DEBUG] Processing Key: &{0xc0000c7b80 0xc0004c2000 Update}
2022/04/01 09:27:15 [DEBUG] [PROV] IPAM LABEL: doesntexist Not Found
2022/04/01 09:27:15 [DEBUG] [PROV] Unsupported IPAM LABEL: doesntexist
Setup Details
FIC Version : 0.1.6 CIS Version : 2.7.1
Description
When I deploy an LB service with an ipamLabel that is wrong, even if I correct it later, this doesn't reflect on the service and it always shows as.
In order this to work I need to change the name of the service.
Steps To Reproduce
1) Deploy a service with an ipamLabel that doesn't exists 2) Redeploy the service with the correct label. 3) Check that the service is in pending mode.
Diagnostic Information
Observations (if any)