Bug 2096434 - [DOCS] [disconnected] Need to configure OCP not to manage DNS on AWS UPI for disconnected installs
Summary: [DOCS] [disconnected] Need to configure OCP not to manage DNS on AWS UPI for ...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 4.11
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.7.z
Assignee: Ben Scott
QA Contact: Yunfei Jiang
Latha S
Depends On:
TreeView+ depends on / blocked
Reported: 2022-06-13 19:58 UTC by Rafael Fonseca
Modified: 2022-09-23 12:09 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-09-23 12:09:26 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 2068180 1 low CLOSED OCP UPI on AWS with STS enabled is breaking the Ingress operator 2022-08-10 19:01:53 UTC

Description Rafael Fonseca 2022-06-13 19:58:30 UTC
Document URL: https://docs.openshift.com/container-platform/4.10/installing/installing_aws/installing-restricted-networks-aws.html#installation-requirements-user-infra_installing-restricted-networks-aws

Section Number and Name: "Installing a cluster on AWS in a restricted network with user-provisioned infrastructure"

Describe the issue: For disconnected clusters, OpenShift can be configured not to manage DNS, and the cluster administrator can configure DNS manually. Otherwise, the ingress operator will try to contact the STS endpoint "sts.amazon.com" directly as opposed to the configured VPC endpoint for the cluster. This could be an issue in cases when the cluster needs to be as air-gapped as possible.

Suggestions for improvement: https://github.com/openshift/installer/pull/5974/files

Additional information:

Note You need to log in before you can comment on or make changes to this bug.