OCPBUGS-86038: [release-4.22] AWS userProvisioned DNS: Obtain Load Balancer IPs from DNS names

[sadasu]

This change obtains the API and API-Int LoadBalancer IP addresses by looking up the IP addresses of the DNSName of APIServerELB (internal LB) and SecondaryAPIServerELB (external LB).

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: cab6bc02-a30f-4d9c-936f-171dae5f4ef4

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sadasu]

/test e2e-aws-custom-dns-techpreview

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign mtulio for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• pkg/infrastructure/aws/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@sadasu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-aws-ovn	9516c51	link	true	/test e2e-aws-ovn
ci/prow/e2e-aws-ovn-imdsv2	9516c51	link	false	/test e2e-aws-ovn-imdsv2
ci/prow/e2e-aws-ovn-single-node	9516c51	link	false	/test e2e-aws-ovn-single-node
ci/prow/e2e-aws-ovn-shared-vpc-custom-security-groups	9516c51	link	false	/test e2e-aws-ovn-shared-vpc-custom-security-groups
ci/prow/e2e-aws-ovn-shared-vpc-edge-zones	9516c51	link	false	/test e2e-aws-ovn-shared-vpc-edge-zones
ci/prow/e2e-aws-ovn-heterogeneous	9516c51	link	false	/test e2e-aws-ovn-heterogeneous
ci/prow/e2e-aws-byo-subnet-role-security-groups	9516c51	link	false	/test e2e-aws-byo-subnet-role-security-groups
ci/prow/e2e-aws-ovn-edge-zones	9516c51	link	false	/test e2e-aws-ovn-edge-zones
ci/prow/e2e-aws-ovn-fips	9516c51	link	false	/test e2e-aws-ovn-fips

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[sadasu]

/payload-job periodic-ci-openshift-openshift-tests-private-release-5.0-multi-nightly-aws-eusc-ipi-custom-dns-mini-perm-tp-amd-f28-destructive
/payload-job periodic-ci-openshift-openshift-tests-private-release-5.0-amd64-nightly-aws-usgov-ipi-custom-dns-mini-perm-tp-f7

[openshift-ci]

@sadasu: trigger 2 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-openshift-tests-private-release-5.0-multi-nightly-aws-eusc-ipi-custom-dns-mini-perm-tp-amd-f28-destructive
• periodic-ci-openshift-openshift-tests-private-release-5.0-amd64-nightly-aws-usgov-ipi-custom-dns-mini-perm-tp-f7

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/dfd962f0-5069-11f1-8221-4cfd715d3e56-0

[sadasu]

/payload-job periodic-ci-openshift-openshift-tests-private-release-4.22-multi-nightly-aws-eusc-ipi-custom-dns-mini-perm-tp-amd-f28-destructive
/payload-job periodic-ci-openshift-openshift-tests-private-release-4.22-amd64-nightly-aws-usgov-ipi-custom-dns-mini-perm-tp-f7

[openshift-ci]

@sadasu: trigger 2 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-openshift-tests-private-release-4.22-multi-nightly-aws-eusc-ipi-custom-dns-mini-perm-tp-amd-f28-destructive
• periodic-ci-openshift-openshift-tests-private-release-4.22-amd64-nightly-aws-usgov-ipi-custom-dns-mini-perm-tp-f7

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/bf72a9e0-5073-11f1-92e3-b3fa36b15b5b-0

[openshift-ci-robot]

@sadasu: This pull request references Jira Issue OCPBUGS-86038, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected Jira Issue OCPBUGS-86038 to depend on a bug targeting a version in 5.0.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

This change obtains the API and API-Int LoadBalancer IP addresses by looking up the IP addresses of the DNSName of APIServerELB (internal LB) and SecondaryAPIServerELB (external LB).

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[sadasu]

/jira refresh

[openshift-ci-robot]

@sadasu: This pull request references Jira Issue OCPBUGS-86038, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected Jira Issue OCPBUGS-86038 to depend on a bug targeting a version in 5.0.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[sadasu]

/label backport-risk-assessed