-
Feature
-
Resolution: Done
-
Major
-
None
-
Product / Portfolio Work
-
-
-
False
-
None
-
False
-
M
-
8
-
None
-
-
-
-
None
-
None
-
None
-
Goal
This goals of this features are:
- As part of a Microsoft guideline/requirement for implementing ARO HCP, we need to design a shared-ingress to kube-apiserver because MSFT has internal restrictions on IPv4 usage. Â
Background
Given Microsoft's constraints on IPv4 usage, there is a pressing need to optimize IP allocation and management within Azure-hosted environments.
Â
Interoperability Considerations
- Impact: Which versions will be impacted by the changes?
- Test Scenarios: Must test across various network and deployment scenarios to ensure compatibility and scale (perf/scale)
- is blocked by
-
NE-1894 Build HAProxy RHEL9 3.0 version
-
- To Do
-
- is depended on by
-
OCPSTRAT-1986 Hosted Cluster Kube API Server Ingress via swift
-
- Refinement
-
- links to
(24 links to)