-
Feature
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
Product / Portfolio Work
-
-
False
-
-
False
-
None
-
None
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
Feature Overview (aka. Goal Summary)
Using the update-agent and MCP capabilities provided in OCPSTRAT-2241 ,a consolidated update experience as part of OCPSTRAT-2620 and built in top of OCPSTRAT-2701 user is provided with an AI-based analysis of all release notes and compatibility statements of all selected OLM-managed operator version targets that highlights any potential risks. These could be failing preflight checks, breaking changes documented in the release notes, version incompatibilities or nearing end-of-life dates.
Goals (aka. expected user outcomes)
Before a user commences with an upgrade they have an accurate assessment of the potential risks and changes involved without having to consult the various different release notes and lifecycle compatibility data sources for the selected operators, provided in the form of a summary in the Console upgrade wizard.
Requirements (aka. Acceptance Criteria):
- Pre-flight check output is analysed
- Release notes of selected OLM-managed operators is analysed
- Cluster-vs.-Operator version compatibility is analysed
- the upgrade risk analysis is a summary of any findings
Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed. Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.
| Deployment considerations | List applicable specific needs (N/A = not applicable) |
| Self-managed, managed, or both | both |
| Classic (standalone cluster) | yes |
| Hosted control planes | yes |
| Multi node, Compact (three node), or Single node (SNO), or all | yes |
| Connected / Restricted Network | has to work in disconnected environments |
| Architectures, e.g. x86_x64, ARM (aarch64), IBM Power (ppc64le), and IBM Z (s390x) | architecture independent |
| Operator compatibility | requires structured exposure of release notes |
| Backport needed (list applicable versions) | no |
| UI need (e.g. OpenShift Console, dynamic plugin, OCM) | described in OCPSTRAT-2620 |
Background
With the pre-work set in OCPSTRAT-2620 and OCPSTRAT-2701 a user has a central entry point into the upgrade experience on the cluster, which now includes both the platform as well as the upgrade of any layered product in the form of Red Hat operators. With information available via APIs and visualized in a single place we have an opportunity to enhance the experience with an AI-generated summary that shorts the analysis of every data point/source provided and proactively guides the user to areas where they should pay attention to.
Customer Considerations
This requires a customer to have OpenShift Lightspeed enabled and connected to an MCP-capable LLM.
- split from
-
-
- New
-
