Skip to content

Commit 08519f1

Browse files
authored
Merge pull request #77665 from bscott-rh/OSDOCS-10955-RN
OSDOCS-10955-RN Adding warning about lack of CAPI testing with secret regions
2 parents 653304c + c51e59f commit 08519f1

File tree

1 file changed

+8
-1
lines changed

1 file changed

+8
-1
lines changed

release_notes/ocp-4-16-release-notes.adoc

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -70,10 +70,15 @@ With this release, you can now install {op-system} to iSCSI boot devices. Multip
7070

7171
[id="ocp-4-16-installation-and-update-aws-capi_{context}"]
7272
==== Cluster API replaces Terraform for AWS installations
73-
In {product-title} {product-version}, the installation program uses Cluster API instead of Terraform to provision cluster infrastructure during installations on AWS. There are several additional required permissions as a result of this change. For more information, see xref:../installing/installing_aws/installing-aws-account.adoc#installation-aws-permissions_installing-aws-account[Required AWS permissions for the IAM user].
73+
In {product-title} {product-version}, the installation program uses Cluster API (CAPI) instead of Terraform to provision cluster infrastructure during installations on AWS. There are several additional required permissions as a result of this change. For more information, see xref:../installing/installing_aws/installing-aws-account.adoc#installation-aws-permissions_installing-aws-account[Required AWS permissions for the IAM user].
7474

7575
Additionally, SSH access to control plane and compute machines is no longer open to the machine network, but is restricted to the security groups associated with the control plane and compute plane machines.
7676

77+
[WARNING]
78+
====
79+
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. There is a known issue with Network Load Balancers' support for security groups in secret or top secret regions that causes installations to fail. For more information, see link:https://issues.redhat.com/browse/OCPBUGS-33311[*OCPBUGS-33311*].
80+
====
81+
7782
[id="ocp-4-16-installation-and-update-optional-ccm_{context}"]
7883
==== Optional cloud controller manager cluster capability
7984

@@ -2017,6 +2022,8 @@ In the following tables, features are marked with the following statuses:
20172022

20182023
* {run-once-operator} (RODOO) cannot be installed on clusters managed by the Hypershift Operator. (link:https://issues.redhat.com/browse/OCPBUGS-17533[*OCPBUGS-17533*])
20192024

2025+
* {product-title} {product-version} installation on {aws-short} in a secret or top secret region fails due to an issue with Network Load Balancers (NLBs) and security groups in these regions. (link:https://issues.redhat.com/browse/OCPBUGS-33311[*OCPBUGS-33311*])
2026+
20202027
* When you run Cloud-native Network Functions (CNF) latency tests on an {product-title} cluster, the `oslat` test can sometimes return results greater than 20 microseconds. This results in an `oslat` test failure.
20212028
(link:https://issues.redhat.com/browse/RHEL-9279[*RHEL-9279*])
20222029

0 commit comments

Comments
 (0)