Prevent leaking EIP when creating machines with BYO IPv4 Pool #5038
Labels
kind/bug
Categorizes issue or PR as related to a bug.
needs-priority
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
/kind bug
What steps did you take and what happened:
[A clear and concise description of what the bug is.]
There are some situations that a machine deployed with BYO IPv4 pool is leaking Elastic IPs:
AssociatePublicIpAddress
) to create the instance without public IP must be set to false to the primary network interface, otherwise the instance will be created with an Amazon-provided while the BYO IP reconciliation loop doesn't reach the BYO reconciliation, and the custom EIP is allocated and associated to the instance.*alternating is expected as the algorithm lookup the EIP by
role
trying to optimize/reuse disassociated.Furthermore, the following failure is happening as the BYO IP reconciliation loop is trying to associate to an non-running machine:
What did you expect to happen:
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
kubectl version
):/etc/os-release
): RHCOSThe text was updated successfully, but these errors were encountered: