This is a clone of issue OCPBUGS-38722. The following is the description of the original issue:
—
Description of problem:
We should add validation in the Installer when public-only subnets is enabled to make sure that: 1. Print a warning if OPENSHIFT_INSTALL_AWS_PUBLIC_ONLY is set 2. If this flag is only applicable for public cluster, we could consider exit earlier if publish: Internal 3. If this flag is only applicable for byo-vpc configuration, we could consider exit earlier if no subnets provided in install-config.
Version-Release number of selected component (if applicable):
all versions that support public-only subnets
How reproducible:
always
Steps to Reproduce:
1. Set OPENSHIFT_INSTALL_AWS_PUBLIC_ONLY 2. Do a cluster install without specifying a VPC. 3.
Actual results:
No warning about the invalid configuration.
Expected results:
Additional info:
This is an internal-only feature, so this validations shouldn't affect the normal path used by customers.
- blocks
-
OCPBUGS-39087 [aws] add validation for public-only subnets workflows
- Closed
- clones
-
OCPBUGS-38722 [aws] add validation for public-only subnets workflows
- Verified
- is blocked by
-
OCPBUGS-38722 [aws] add validation for public-only subnets workflows
- Verified
- is cloned by
-
OCPBUGS-39087 [aws] add validation for public-only subnets workflows
- Closed
- links to
-
RHEA-2024:3718 OpenShift Container Platform 4.17.z bug fix update