Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

✨ Support BYO Public IPv4 Pool when provision infrastructure #4905

Merged
merged 1 commit into from
Jun 12, 2024

Commits on Jun 7, 2024

  1. ✨ Support BYO Public IPv4 Pool for Elastic IPs

    Introducing support of BYO Public IPv4 Pool to allow CAPA allocate
    IPv4 Elastic IPs from user-provided IPv4 pools that was brought to
    AWS when provisioning base cluster infrastructure.
    
    This change introduce the API fields:
    - AWSCLuster NetworkSpec.ElasticIPPool: allowing
    the controllers to consume from user-provided public pools when provisioning
    core components from the infrastructure, like Nat Gateways and public
    Network Load Balancer (API server only)
    - AWSMachine ElasticIPPool: allowing the machine to consume from BYO
      Public IPv4 pool when the instance is deployed in the public subnets.
    
    The ElasticIPPool structure defines a custom IPv4 Pool (previously
    created in the AWS Account) to teach controllers to set the pool when
    creating public ip addresses (Elastic IPs) for components which requires
    it, such as Nat Gateways and NLBs.
    mtulio committed Jun 7, 2024
    Configuration menu
    Copy the full SHA
    2f230b3 View commit details
    Browse the repository at this point in the history