XML

Word

Printable

Type: Epic
Resolution: Unresolved
Priority: Normal
Fix Version/s: None
Affects Version/s: None
Labels:
- 4.18-candidate
- CAPI

Epic Name:
CAPI
Work Type:
BU Product Work
Blocked:
False
Ready:
False
Epic Status:
To Do
Feature Link:
OCPSTRAT-681 - Integrate Cluster API (CAPI) in standalone OCP-Phase 4
Parent Link:
OCPSTRAT-681Integrate Cluster API (CAPI) in standalone OCP-Phase 4
Hierarchy Progress Bar:

100% To Do, 0% In Progress, 0% Done

SFDC Cases Links:
SFDC Cases Counter:
SFDC Cases Open:

Epic Goal

Support initial implementation of CAPI in 4.13? timeframe

Why is this important?

…

Scenarios

...

Acceptance Criteria

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>

is caused by

OCPPLAN-7719 Cluster API integration

New

links to

Steps towards CAPI based IPI clusters

Assignee:: Unassigned

Reporter:: Mike Worthington

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Created:: 2022/01/18 3:47 PM

Updated:: 2024/09/04 9:54 PM