-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
CAPA Dual Stack Support for unmanaged clusters
-
Product / Portfolio Work
-
-
18% To Do, 59% In Progress, 24% Done
-
False
-
-
False
-
Not Selected
-
None
-
None
OCP/Telco Definition of Done
Epic Template descriptions and documentation.
<--- Cut-n-Paste the entire contents of this description into your new Epic --->
Epic Goal
To allow single-stack ipv6 installs on AWS:
- Evaluate current CAPA support for IPv6 unmanaged clusters (managed EKS clusters seem to have complete IPv6 support)
- Open upstream CAPA PRs to bridge gaps in support
Why is this important?
- Allowing choice between ipv4 & ipv6 allows more user opportunities, particularly to meet federal requirements
Scenarios
- ...
Acceptance Criteria
- It is not necessary to be completely 100% ipv6. For example, Azure still has ipv4 node addresses. Achieving as much ipv6 coverage as possible is the goal.
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- ...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- …
Open questions::
- …
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Enablement <link to Feature Enablement Presentation>
- DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
- DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
- DEV - Downstream build attached to advisory: <link to errata>
- QE - Test plans in Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Downstream documentation merged: <link to meaningful PR>
