Skip to content

Commit

Permalink
Bug 2068180: update doc for DNS and disconnected clusters
Browse files Browse the repository at this point in the history
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 sts directly
"sts.amazonaws.com" as opposed to the configured VPC endpoint for the
cluster.
  • Loading branch information
r4f4 committed Jun 7, 2022
1 parent 2ca5014 commit ea9cf16
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions docs/user/aws/install_upi.md
Original file line number Diff line number Diff line change
Expand Up @@ -114,6 +114,10 @@ open(path, "w").write(yaml.dump(data, default_flow_style=False))'

If you do so, you'll need to [add ingress DNS records manually](#add-the-ingress-dns-records) later on.

#### Disconnected clusters

For disconnected clusters, Openshift has to be configured [not to manage DNS](#remove-dns-zones), otherwise [the ingress operator][ingress-operator] will try to contact the STS endpoint "sts.amazon.com" directly as opposed to the configured VPC endpoint for the cluster.

## Create Ignition Configs

Now we can create the bootstrap Ignition configs:
Expand Down

0 comments on commit ea9cf16

Please sign in to comment.