openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 21:46:22 +01:00
Code Issues Releases Activity

OSDOCS-17448:Updated the procedure formatting to show numbered steps.

Browse Source
This commit is contained in:
John Heraghty
2026-01-09 15:27:32 +00:00
committed by openshift-cherrypick-robot
parent 32c11168c3
commit 22fdd77ef9
1 changed files with 10 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
modules/mos-checklist-vpc-privatelink.adoc
View File

@@ -11,22 +11,22 @@ If you choose to deploy a PrivateLink cluster, then be sure to deploy the cluste
include::snippets/snip_install-cluster-in-vpc.adoc[]
.Procedure
* Create a public and private subnet for each AZ that your cluster uses.
** Alternatively, implement transit gateway for internet and egress with appropriate routes.
* The VPC's CIDR block must contain the `Networking.MachineCIDR` range, which is the IP address for cluster machines.
** The subnet CIDR blocks must belong to the machine CIDR that you specify.
* Set both `enableDnsHostnames` and `enableDnsSupport` to `true`.
** That way, the cluster can use the Route 53 zones that are attached to the VPC to resolve cluster internal DNS records.
* Verify route tables by running:
. Create a public and private subnet for each AZ that your cluster uses.
* Alternatively, implement transit gateway for internet and egress with appropriate routes.
. The VPC's CIDR block must contain the `Networking.MachineCIDR` range, which is the IP address for cluster machines.
* The subnet CIDR blocks must belong to the machine CIDR that you specify.
. Set both `enableDnsHostnames` and `enableDnsSupport` to `true`.
* That way, the cluster can use the Route 53 zones that are attached to the VPC to resolve cluster internal DNS records.
. Verify route tables by running:
+
[source,terminal]
----
$ aws ec2 describe-route-tables --filters "Name=vpc-id,Values=<vpc-id>"
----
+
** Ensure that the cluster can egress either through NAT gateway in public subnet or through transit gateway.
** Ensure whatever UDR you want to follow is set up.
* You can also configure a cluster-wide proxy during or after install.
.. Ensure that the cluster can egress either through NAT gateway in public subnet or through transit gateway.
.. Ensure whatever UDR you want to follow is set up.
. You can also configure a cluster-wide proxy during or after install.
+
[NOTE]
====