1. Proposed title of this feature request

Support Single-Stack IPv6 for ACM and HyperShift Based Deployments

2. What is the nature and description of the request?

ACM-managed and HyperShift-hosted clusters currently assume IPv4 or dual-stack connectivity for management traffic, cluster registration, and service publishing.

There is no supported path to deploy or manage clusters in single-stack IPv6-only environments, limiting OpenShift adoption in IPv6-mandated infrastructures.

Problem Statement

Current gaps include:

1. Managed Cluster Registration

• • Klusterlet registration assumes IPv4 reachability.

• • IPv6-only managed clusters fail to register or remain degraded.

1. HyperShift Hosted Control Planes

• • Service publishing strategies (NodePort / LB) are IPv4-centric.

• • IPv6-only API and ingress endpoints are not validated.

1. Management Plane Communication

• • ACM ↔ managed cluster communication paths rely on IPv4.

• • No validation for IPv6-only hub-to-spoke connectivity.

1. Networking & Validation

• • Lack of CI coverage for IPv6-only ACM/HyperShift flows.

• • No clear error messages when unsupported IPv6-only configs are used.

1. Documentation & Supportability

• • No official guidance for IPv6-only ACM or HyperShift deployments.

• • No support statement for IPv6-only managed or hosted clusters.

---

Proposed Enhancement

Enable full IPv6-only lifecycle support for ACM and HyperShift:

• IPv6-only managed cluster registration and health reporting

• IPv6-only Klusterlet communication

• IPv6-only hosted control plane service publishing

• IPv6-only API and ingress endpoints

• Validation and CI coverage for IPv6-only management paths

• Clear documentation and support boundaries

---

Use Cases / Customer Impact

• Centralized management of IPv6-only fleets

• Hosted control planes in IPv6-only environments

• Edge and bare-metal deployments at scale

• Regulated industries where IPv4 is prohibited

Without this enhancement, customers must:

• Maintain IPv4 for management traffic

• Use unsupported workarounds

• Avoid ACM and HyperShift for IPv6-only environments

---

Acceptance Criteria

• ACM can successfully manage IPv6-only clusters

• HyperShift hosted clusters function without IPv4

• Documented and supported IPv6-only configurations

• Automated testing validating IPv6-only flows

---

 

3. Why does the customer need this? (List the business requirements here)

Without this enhancement, customers must retain IPv4 solely for installation or avoid ACM/HCP installation entirely.

4. List any affected packages or components.