Skip to content

OSDOCS:16105_RN:adding AWS DNS RN#104693

Merged
bscott-rh merged 1 commit intoopenshift:enterprise-4.21from
brendan-daly-red-hat:OSDOCS-16105_RN
Jan 30, 2026
Merged

OSDOCS:16105_RN:adding AWS DNS RN#104693
bscott-rh merged 1 commit intoopenshift:enterprise-4.21from
brendan-daly-red-hat:OSDOCS-16105_RN

Conversation

@brendan-daly-red-hat
Copy link
Contributor

@brendan-daly-red-hat brendan-daly-red-hat commented Jan 13, 2026

Version:
4.21

Issue:
https://issues.redhat.com/browse/OSDOCS-17856

Link to docs preview:
Installing a cluster on AWS with a user-provisioned DNS (Technology Preview)

QE review:

  • QE has approved this change.

Additional information:
This is the feature PR for this release note: #98724.

@openshift-ci openshift-ci bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Jan 13, 2026
@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Jan 13, 2026

🤖 Fri Jan 30 14:20:01 - Prow CI generated the docs preview:

https://104693--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-21-release-notes.html

@brendan-daly-red-hat brendan-daly-red-hat changed the title OSDOCS:16105_RN:adding RN OSDOCS:16105_RN:adding AWS DNS RN Jan 19, 2026
@brendan-daly-red-hat brendan-daly-red-hat force-pushed the OSDOCS-16105_RN branch 4 times, most recently from 77689f5 to 21afe9d Compare January 26, 2026 15:28
@brendan-daly-red-hat brendan-daly-red-hat force-pushed the OSDOCS-16105_RN branch 2 times, most recently from 068e939 to 752cef3 Compare January 27, 2026 08:46
@brendan-daly-red-hat
Copy link
Contributor Author

@yunjiang29, PTAL

@brendan-daly-red-hat brendan-daly-red-hat force-pushed the OSDOCS-16105_RN branch 2 times, most recently from 55f410d to 0a94407 Compare January 27, 2026 17:48
@yunjiang29
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 28, 2026
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Jan 28, 2026
@brendan-daly-red-hat
Copy link
Contributor Author

@yunjiang29, PTAL

+
You can enable a user-provisioned domain name server (DNS) instead of the default cluster-provisioned DNS solution. For example, your organization's security policies might not allow the use of public DNS services such as {aws-first} DNS. As a result, you can manage the API and Ingress DNS records in your own system rather than adding the records to the DNS of the cloud. If you use this feature, you must provide your own DNS solution that includes records for `api.<cluster_name>.<base_domain>.` and `*.apps.<cluster_name>.<base_domain>.`. Enabling a user-provisioned DNS is available as a Technology Preview feature.
+
For more information, see xref:../installing/installing_aws/ipi/installing-restricted-networks-aws-installer-provisioned.adoc#installation-aws-enabling-user-managed-DNS_installing-restricted-networks-aws-installer-provisioned[Enabling a user-managed DNS] and xref:../installing/installing_aws/ipi/installing-restricted-networks-aws-installer-provisioned.adoc#installation-aws-provisioning-own-dns-records_installing-restricted-networks-aws-installer-provisioned[Provisioning your own DNS records].
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it looks like the links are the same and point to the same restricted-networks cluster chapter, can we use a common cluster instead? Like:

Installing a cluster on AWS with customizations

Enabling a user-managed DNS
Provisioning your own DNS records

@brendan-daly-red-hat brendan-daly-red-hat force-pushed the OSDOCS-16105_RN branch 2 times, most recently from 0cdc5aa to 71e033d Compare January 29, 2026 10:31
+
You can enable a user-provisioned domain name server (DNS) instead of the default cluster-provisioned DNS solution. For example, your organization's security policies might not allow the use of public DNS services such as {aws-first} DNS. As a result, you can manage the API and Ingress DNS records in your own system rather than adding the records to the DNS of the cloud. If you use this feature, you must provide your own DNS solution that includes records for `api.<cluster_name>.<base_domain>.` and `*.apps.<cluster_name>.<base_domain>.`. Enabling a user-provisioned DNS is available as a Technology Preview feature.
+
For more information, see xref:../installing/installing_aws/ipi/installing-aws-customizations.adoc#installation-aws-enabling-user-managed-DNS_installing-restricted-networks-aws-installer-provisioned[Enabling a user-managed DNS] and xref:../installing/installing_aws/ipi/installing-aws-customizations.adoc#installation-aws-provisioning-own-dns-records_installing-restricted-networks-aws-installer-provisioned[Provisioning your own DNS records].
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it looks like the link does not work, need to wait for #98724 get merged?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, #98724 must be merged for the link to work. Can you add 'LGTM' here?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought the links should like:

https://98724--ocpdocs-pr.netlify.app/openshift-enterprise/latest/installing/installing_aws/ipi/installing-aws-customizations#installation-aws-enabling-user-managed-DNS_installing-aws-customizations

and

https://98724--ocpdocs-pr.netlify.app/openshift-enterprise/latest/installing/installing_aws/ipi/installing-aws-customizations#installation-aws-provisioning-own-dns-records_installing-aws-customizations

@openshift-ci
Copy link

openshift-ci bot commented Jan 30, 2026

@brendan-daly-red-hat: all tests passed!

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
Copy link

sadasu commented Jan 30, 2026

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 30, 2026
@bscott-rh bscott-rh added branch/enterprise-4.21 merge-review-in-progress Signifies that the merge review team is reviewing this PR labels Jan 30, 2026
@bscott-rh bscott-rh added this to the Planned for 4.21 GA milestone Jan 30, 2026
Copy link
Contributor

@bscott-rh bscott-rh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Merge review LGTM.

@bscott-rh bscott-rh merged commit 59c29be into openshift:enterprise-4.21 Jan 30, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.21 lgtm Indicates that a PR is ready to be merged. merge-review-in-progress Signifies that the merge review team is reviewing this PR size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants