Multi-Pool: status.ipam.operator-status.error
is not cleared after a successful allocation
#28758
Open
2 tasks done
Labels
area/ipam
Impacts IP address management functionality.
area/multipool
Affects Multi-Pool IPAM
kind/bug
This is a bug in the Cilium logic.
sig/agent
Cilium agent related.
sig/ipam
IP address management, including cloud IPAM
Is there an existing issue for this?
What happened?
To reproduce, create Cilium installation without default pool, create default pool after one minute, and observe nodes successfully allocating pod CIDRs from default pool, but still reports
cannot allocate from non-existing pool: default error is not cleared
Cilium Version
Affects versions 1.14.0 up to current
main
Kernel Version
N/A
Kubernetes Version
N/A
Sysdump
No response
Relevant log output
No response
Anything else?
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: