{}USER STORY:{}

• As a CAPA user, I would like to decrease the impact of additional cost of Public IPv4 charges (introduced by AWS in February 2024) in my CI cluster pool consuming thousands clusters/day from Amazon-provided IPv4 pool (default), so I can keep the total cost of my fleet under control.
• As a CAPA user, I would like to be able to deploy clusters consuming public IPv4 from my custom [IPv4 pool that I brought to AWS][byoip], so I can have control of public IPs used by my clusters.

{}DESCRIPTION:{}

Goal:

• Create a PR on installer setting the CAPA to create public resources (EIP) consuming from PublicIPv4Pool
  • The PR must include the draft of upstream proposal (which BYO IP is not currently supported)

{}Required:{}

...

{}Nice to have:{}

...

{}ACCEPTANCE CRITERIA:{}

• Presubmit using Public IPv4 Pool is passing
• Installer PR is merged

{}ENGINEERING DETAILS:{}