Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-35504

Feature parity with BYO Public IPv4 terraform in CAPA

XMLWordPrintable

    • No
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, the installation program on {aws-first} used multiple IPv4 public IP addresses that Amazon has started charging for. With this release, support is provided for bring your own (BYO) public IPv4 pools in {product-title} so that users have control of IP addresses that are used by their services. Where the BYO public IPv4 pools feature is enabled, two new permissions, `ec2:DescribePublicIpv4Pools` and `ec2:DisassociateAddress`, are required, and the issue is resolved. (link:https://issues.redhat.com/browse/OCPBUGS-35504[*OCPBUGS-35504*])
      Show
      * Previously, the installation program on {aws-first} used multiple IPv4 public IP addresses that Amazon has started charging for. With this release, support is provided for bring your own (BYO) public IPv4 pools in {product-title} so that users have control of IP addresses that are used by their services. Where the BYO public IPv4 pools feature is enabled, two new permissions, `ec2:DescribePublicIpv4Pools` and `ec2:DisassociateAddress`, are required, and the issue is resolved. (link: https://issues.redhat.com/browse/OCPBUGS-35504 [* OCPBUGS-35504 *])
    • Bug Fix
    • Done

      Description of problem:

      The BYO Public IPv4 feature[1] for AWS added on Terraform version[2] was merged on capi upstream/CAPA[3] after branch cut. The installer PR supporting CAPA provisioning BYO IPv4 was also merged[4] in the active branch (4.17).

The feature is exercised by CI tests[5][6], the step[7] is running by default on CI runs to consume from existing CI IPv4 Pool when using terraform version.

[1] https://issues.redhat.com/browse/OCPSTRAT-1154
[2] https://issues.redhat.com/browse/SPLAT-1432 https://github.com/openshift/installer/pull/7983
[3] https://github.com/kubernetes-sigs/cluster-api-provider-aws/pull/4905
[4] https://github.com/openshift/installer/pull/7983
[5] https://github.com/openshift/release/pull/48467
[6] https://github.com/openshift/release/pull/50653
[7] https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openshift_installer/8592/pull-ci-openshift-installer-master-e2e-aws-ovn/1801525554881499136/artifacts/e2e-aws-ovn/ipi-conf-aws-byo-ipv4-pool-public/build-log.txt

      Version-Release number of selected component (if applicable):

      4.16

      How reproducible:

      always

      Steps to Reproduce:

      1. create a cluster with setting platform.aws.publicIpv4Pool on install-config.yaml.
2. create a cluster with CAPA on 4.16

      Actual results:

      the field will be ignored

      Expected results:

      installer provision resources claiming public IPv4 IPs from custom pools provided by AWS.

      Additional info:

       

       

            padillon Patrick Dillon
            rhn-support-mrbraga Marco Braga
            Yunfei Jiang Yunfei Jiang
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: