-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
HCP: Create Cluster to optionally provide Public API Server endpoint
-
Product / Portfolio Work
-
False
-
-
False
-
To Do
-
100% To Do, 0% In Progress, 0% Done
-
-
-
(2/9) Roberto Emanuel wrote on 2025/12/22: "Bala Hi, this effort is targeting HCP specifically. We have a similar scenario in the ROSA and OSD wizards. Should we do the same there? Does it make sense to keep it an HCP only change?"
Overview
Today customers can only configure the visibility of the application ingress on day 2, for this work the option to configure day 1 will be enabled independently from the API visibility
Acceptance Criteria
Additional changes:
- Preflights will validate that only public subnets are required when a cluster has a "Public Ingress".
- ROSA UI Interactive flow can skip public subnets on Private Ingress clusters.
On day two, operations will remain as they are:
- Users can change cluster API visibility in day two.
- Users can change ingress visibiblity in day two.
- Changes on API visibility won't trigger any subnet validation.
- Changes on Ingress visibility will require that public Ingress will contain at least one public subnet in the VPC.