-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
hcp-static-ip
-
Incidents & Support
-
77
-
False
-
-
False
-
- No docs
- No UXD
- No QE
- Document listing our options to allow users to manage IPs of HCP tenants connected to a localnet network without a need to provide a DHCP server
-
None
-
Red
-
To Do
-
0% To Do, 100% In Progress, 0% Done
-
doc-ready, qe-ready, ux-ready
-
Goal
Allow users to define IPs, DNS, and GW configuration on their NodePools.
User Stories
- As a cluster admin defining a new HCP cluster connected directly to the underlay VLAN,
I want to define static IP assignment and GW / DNS configuration on the NodePool,
so I don't have to run a DHCP server on my network,
and so I can define firewall rules matching those known static IPs.
Non-Requirements
- <List of things not included in this epic, to alleviate any doubt raised during the grooming process.>
Notes
- This should mimick the approach of assisted installer for on-prem deployments, where the user requests specific IPs for their nodes. See https://docs.redhat.com/en/documentation/assisted_installer_for_openshift_container_platform/2025/html-single/installing_openshift_container_platform_with_the_assisted_installer/index#configuring-static-networks_installing-with-ui
1.
|
upstream roadmap issue |
|
New | 
|
Unassigned |
2.
|
upstream documentation |
|
Closed |
|
Unassigned |
3.
|
upgrade consideration |
|
New |
|
Unassigned |
4.
|
test plans in polarion |
|
Closed |
|
Unassigned |
5.
|
automated tests |
|
Closed |
|
Unassigned |
6.
|
downstream documentation merged |
|
Closed |
|
Unassigned |
7.
|
CNV QE DevOps Requirement/Enablement |
|
Closed |
|
Unassigned |