Feature Overview (aka. Goal Summary)  

Using the update-agent and MCP capabilities provided in OCPSTRAT-2241 and a update risk analysis provided in OCPSTRAT-2701 users can leverage an agent to automatically apply z-stream patches and optionally y-stream updates of selected operators or the cluster if the update risk analysis yields negligible to no risk.

Goals (aka. expected user outcomes)

Users update more frequently and thereby improve their security posture and proactively get ahead of issues fixed by z-stream/y-stream updates with confidence backed by a holistic analysis of update risks beforehand. We can divide update into two categories: one that can simply be applied (in combination with a scheduled maintenance window (OCPSTRAT-1696) and those that actually need attention by a platform engineering team.

Requirements (aka. Acceptance Criteria):

• risk level classification is available
• the update risk analysis (OCPSTRAT-2701) is leveraging the established risk level classification
• a user can select their risk acceptance in accordance to a provided level
• selected update types (z-stream, y-stream) of the cluster or selected operators are applied automatically if they pass the risk acceptance of the customer
• scheduled updates honor defined maintenance windows

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.

Background

User are often reluctant to apply updates, even z-stream updates which should simply be able to be applied at all times due to lack of bandwidth to comprehensivesly analyze risk beforehand. We can use the automatic analysis provided in OCPSTRAT-2701 to categorize updates as "safe to apply" and apply selected types automatically, alleviating the need for the user to do this classification by themselves.

Customer Considerations

This requires a customer to have OpenShift Lightspeed enabled and connected to an MCP-capable LLM.