From 22fdd77ef91ddcf40afa6e26d14f26f30c8dafdd Mon Sep 17 00:00:00 2001 From: John Heraghty Date: Fri, 9 Jan 2026 15:27:32 +0000 Subject: [PATCH] OSDOCS-17448:Updated the procedure formatting to show numbered steps. --- modules/mos-checklist-vpc-privatelink.adoc | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/modules/mos-checklist-vpc-privatelink.adoc b/modules/mos-checklist-vpc-privatelink.adoc index 6aa03e9746..9b479a70ae 100644 --- a/modules/mos-checklist-vpc-privatelink.adoc +++ b/modules/mos-checklist-vpc-privatelink.adoc @@ -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=" ---- + -** 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] ====