-
Bug
-
Resolution: Done-Errata
-
Normal
-
4.14.z, 4.15.z, 4.16
This is a clone of issue OCPBUGS-38963. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-33308. The following is the description of the original issue:
—
Description of problem:
When creating an OCP cluster on AWS and selecting "publish: Internal," the ingress operator may create external LB mappings to external subnets. This can occur if public subnets were specified during installation at install-config. https://docs.openshift.com/container-platform/4.15/installing/installing_aws/installing-aws-private.html#private-clusters-about-aws_installing-aws-private A configuration validation should be added to the installer.
Version-Release number of selected component (if applicable):
4.14+ probably older versions as well.
How reproducible:
always
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
Slack thread: https://redhat-internal.slack.com/archives/C68TNFWA2/p1714986876688959
- clones
-
OCPBUGS-38963 IngressController subnet selection in AWS
- Closed
- is blocked by
-
OCPBUGS-38963 IngressController subnet selection in AWS
- Closed
- links to
-
RHBA-2024:7174 OpenShift Container Platform 4.16.z bug fix update