-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
Control plane updates N+3
-
Product / Portfolio Work
-
OCPSTRAT-1587Expand Control Plane Only Updates to 4.N to 4.N+2 and 4.N+3 independent of EUS versions
-
100% To Do, 0% In Progress, 0% Done
-
False
-
-
False
-
Not Selected
-
None
-
None
-
None
Epic Goal*
The feature, OCPSTRAT-1587 aims to enable a control plane-only update(previously called EUS-to-EUS updates) that allows for a three-minor-version (N+3) skew between the control plane and worker nodes
Why is this important? (mandatory)
See the parent
Scenarios (mandatory)
Dependencies (internal and external) (mandatory)
Someone (OTA?) prepares a CI job with N+3 upgrades.
Contributing Teams(and contacts) (mandatory)
- Development -
- QE -
Acceptance Criteria (optional)
Provide some (testable) examples of how we will know if we have achieved the epic goal.
Drawbacks or Risk (optional)
Reasons we should consider NOT doing this such as: limited audience for the feature, feature will be superseded by other work that is planned, resulting feature will introduce substantial administrative complexity or user confusion, etc.
Done - Checklist (mandatory)
The following points apply to all epics and are what the OpenShift team believes are the minimum set of criteria that epics should meet for us to consider them potentially shippable. We request that epic owners modify this list to reflect the work to be completed in order to produce something that is potentially shippable.
- CI Testing - Basic e2e automationTests are merged and completing successfully
- Documentation - Content development is complete.
- QE - Test scenarios are written and executed successfully.
- Technical Enablement - Slides are complete (if requested by PLM)
- Engineering Stories Merged
- All associated work items with the Epic are closed
- Epic status should be “Release Pending”