-
Initiative
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
False
-
-
False
-
Not Selected
-
100% To Do, 0% In Progress, 0% Done
-
0
Goals
What is our purpose in implementing this? What are we enabling by doing this work? Time-box goals to 4-6 months.
- Document the top reasons customers need a Support exception to extend support of specific OpenShift versions
- Create solutions to enable customers to upgrade OpenShift clusters in more timely manner
Benefit Hypothesis:
What are the benefits (to Red Hat, eventually to customers, to the community, etc.)? Does it improve security, performance, supportability, etc? Why is work a priority? We believe that the result of doing this work will be ...
- The most common support exception in 2024 is the EOL type support exception. Customers are asking for more time to upgrade their clusters on a normal basis. When a customer opens these support exception that version of Openshift is no longer supported. Enabling customers to keep their clusters "up to date" will improve the security and supportability of their clusters.
Resources
Add any resources (docs, slides, etc.) pertinent to the definition of the work. These might not be known until later. Update as necessary.
- SUPPORT-EX Dashboard: https://issues.redhat.com/secure/Dashboard.jspa?selectPageId=12352192
Responsibilities
Indicate which roles and/or teams will be responsible for contributing to the initiative and generally what they might be expected to do.
- BU/Management:
- Identify customers to work with
- SD Engineering Teams:
- Investigation and Engineering work
Success Criteria
Provide some examples of how we will know if we have achieved the goal. What can be measured to determine success? What observable actions/outcomes that can be seen to determine success? Specific, Measurable, Achievable, fits within the Time-box.
Results
Add results here once the Initiative is started. Recommend discussions & updates once per quarter in bullets.