Merge pull request #60117 from smunje1/OSDOCS-5746

OSDOCS-5746

Author: stevsmit

modules/rosa-sts-creating-a-cluster-with-customizations-cli.adoc

@@ -206,6 +206,11 @@ You can reference the ARN of your KMS key when you create the cluster in the nex
 
 . Create a cluster with STS using custom installation options. You can use the `--interactive` mode to interactively specify custom settings:
 +
+[IMPORTANT]
+====
+To avoid cluster failure issues, do not install a ROSA cluster in an existing VPC created by the previous cluster's ROSA installer. If the cluster that created the VPC during the installation is deleted, the associated installer-created VPC also gets deleted, resulting in the failure of all the clusters installed in the same VPC.
+====
++
 [source,terminal]
 ----
 $ rosa create cluster --interactive --sts

modules/rosa-sts-creating-a-cluster-with-customizations-ocm.adoc

@@ -284,6 +284,11 @@ If you are using private API endpoints, you cannot access your cluster until you
 
 . Optional: If you opted to use public API endpoints, by default a new VPC is created for your cluster. If you want to install your cluster in an existing VPC instead, select *Install into an existing VPC*.
 +
+[IMPORTANT]
+====
+To avoid cluster failure issues, do not install a ROSA cluster in an existing VPC created by the previous cluster's ROSA installer. If the cluster that created the VPC during the installation is deleted, the associated installer-created VPC also gets deleted, resulting in the failure of all the clusters installed in the same VPC.
+====
++
 [NOTE]
 ====
 If you opted to use private API endpoints, you must use an existing VPC and PrivateLink and the *Install into an existing VPC* and *Use a PrivateLink* options are automatically selected. With these options, the Red Hat Site Reliability Engineering (SRE) team can connect to the cluster to assist with support by using only AWS PrivateLink endpoints.