Skip to content

Commit 9d4f9e9

Browse files
authored
Merge pull request #78052 from bscott-rh/fixing-capi-names-main
Removing use of 'CAPI' from AWS install
2 parents 5908018 + e85f5b9 commit 9d4f9e9

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

installing/installing_aws/ipi/installing-aws-secret-region.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ To configure a cluster in either region, you change parameters in the `install c
1515

1616
[WARNING]
1717
====
18-
In {product-title} {product-version}, the installation program uses Cluster API (CAPI) instead of Terraform to provision cluster infrastructure during installations on AWS. Installing a cluster on AWS into a secret or top-secret region has not been tested with CAPI as of the release of {product-title} {product-version}. This document will be updated when installation into a secret region has been tested.
18+
In {product-title} {product-version}, the installation program uses Cluster API instead of Terraform to provision cluster infrastructure during installations on AWS. Installing a cluster on AWS into a secret or top-secret region by using the Cluster API implementation has not been tested as of the release of {product-title} {product-version}. This document will be updated when installation into a secret region has been tested.
1919
2020
There is a known issue with Network Load Balancers' support for security groups in secret or top secret regions that causes installations in these regions to fail. For more information, see link:https://issues.redhat.com/browse/OCPBUGS-33311[OCPBUGS-33311].
2121
====

0 commit comments

Comments
 (0)