Skip to content

[enterprise-4.15] OSDOCS#8632: Updating IMPORTANT admonition regarding installer created VPCs #68449

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 28, 2023
Merged

[enterprise-4.15] OSDOCS#8632: Updating IMPORTANT admonition regarding installer created VPCs #68449

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 8 additions & 4 deletions modules/rosa-sts-creating-a-cluster-with-customizations-cli.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -196,9 +196,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]
[WARNING]
====
You cannot install a ROSA cluster into an existing managed VPC. Managed VPCs are created during the managed cluster deployment process, and must only be associated with a single cluster to ensure that cluster provisioning and deletion operations work correctly. To determine whether a VPC is managed, look for the `red-hat-managed` tag; managed VPCs are tagged with `red-hat-managed:true`.
You cannot install a ROSA cluster into an existing VPC that was created by the OpenShift installer. These VPCs are created during the cluster deployment process and must only be associated with a single cluster to ensure that cluster provisioning and deletion operations work correctly.

To verify whether a VPC was created by the OpenShift installer, check for the `owned` value on the `kubernetes.io/cluster/<infra-id>` tag. For example, when viewing the tags for the VPC named `mycluster-12abc-34def`, the `kubernetes.io/cluster/mycluster-12abc-34def` tag has a value of `owned`. Therefore, the VPC was created by the installer and must not be modified by the administrator.
====
+
[source,terminal]
Expand Down Expand Up @@ -280,9 +282,11 @@ Tags that are added by Red Hat are required for clusters to stay in compliance w
<7> Optional: Multiple availability zones are recommended for production workloads. The default is a single availability zone.
<8> Optional: You can create a cluster in an existing VPC, or ROSA can create a new VPC to use.
+
[IMPORTANT]
[WARNING]
====
You cannot install a ROSA cluster into an existing managed VPC. Managed VPCs are created during the managed cluster deployment process, and must only be associated with a single cluster to ensure that cluster provisioning and deletion operations work correctly. To determine whether a VPC is managed, look for the `red-hat-managed` tag; managed VPCs are tagged with `red-hat-managed:true`.
You cannot install a ROSA cluster into an existing VPC that was created by the OpenShift installer. These VPCs are created during the cluster deployment process and must only be associated with a single cluster to ensure that cluster provisioning and deletion operations work correctly.

To verify whether a VPC was created by the OpenShift installer, check for the `owned` value on the `kubernetes.io/cluster/<infra-id>` tag. For example, when viewing the tags for the VPC named `mycluster-12abc-34def`, the `kubernetes.io/cluster/mycluster-12abc-34def` tag has a value of `owned`. Therefore, the VPC was created by the installer and must not be modified by the administrator.
====
<9> Optional: Enable this option if you are using your own AWS KMS key to encrypt the control plane, infrastructure, worker node root volumes, and PVs. Specify the ARN for the KMS key that you added to the account-wide role ARN in the preceding step.
+
Expand Down
6 changes: 4 additions & 2 deletions modules/rosa-sts-creating-a-cluster-with-customizations-ocm.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -281,9 +281,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]
[WARNING]
====
You cannot install a ROSA cluster into an existing managed VPC. Managed VPCs are created during the managed cluster deployment process, and must only be associated with a single cluster to ensure that cluster provisioning and deletion operations work correctly. To determine whether a VPC is managed, look for the `red-hat-managed` tag; managed VPCs are tagged with `red-hat-managed:true`.
You cannot install a ROSA cluster into an existing VPC that was created by the OpenShift installer. These VPCs are created during the cluster deployment process and must only be associated with a single cluster to ensure that cluster provisioning and deletion operations work correctly.

To verify whether a VPC was created by the OpenShift installer, check for the `owned` value on the `kubernetes.io/cluster/<infra-id>` tag. For example, when viewing the tags for the VPC named `mycluster-12abc-34def`, the `kubernetes.io/cluster/mycluster-12abc-34def` tag has a value of `owned`. Therefore, the VPC was created by the installer and must not be modified by the administrator.
====
+
[NOTE]
Expand Down