Epic Goal*

• Documentation is updated to change references from "EUS-to-EUS" updates to "Control Plane Only Updates" so that it's clear that you may update across EUS versions without EUS entitlements in 4.12 and later
  • In already GA'd versions which are updated the header should indicate "Previously referred to as EUS to EUS updates"
  • In 4.10 documentation mention that "In 4.12 and later this has been renamed to Control Plane Only Updates

Why is this important? (mandatory)

Customers want to perform EUS-to-EUS style updates, where workers are updated only once without having subscriptions which grant access to EUS. While there's no technical barrier to doing so, the naming of the feature implies that this is something unique to EUS subscriptions. Therefore we will rename this and evolve it over time to be even more flexible. The first step will be updating documentation to stop calling it EUS to EUS updates and instead some variation of applying multiple control plane updates with single worker updates.

Scenarios (mandatory) 

Provide details for user scenarios including actions to be performed, platform specifications, and user personas.  

1. A customer wishing to update from 4.12 to 4.14, 4.14 to 4.16 can follow documentation that makes it clear they can apply multiple control plane updates without having EUS entitelements
2. Customers can perform this update by changing from stable-4.12 to stable-4.14 and stable-4.14 to stable-4.16 without running into dead ends

Dependencies (internal and external) (mandatory)

What items must be delivered by other teams/groups to enable delivery of this epic. 

Contributing Teams(and contacts) (mandatory) 

Our expectation is that teams would modify the list below to fit the epic. Some epics may not need all the default groups but what is included here should accurately reflect who will be involved in delivering the epic.

• Development - 
• Documentation -
• QE - 
• PX - 
• Others -

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 - Tests 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)
• Other