EPIC Goal

What are we trying to solve here?

We plan to investigate the process of patching OpenShift AI dependency for the Model Catalog Connector to version 3 to best determine the maintenance schedule of the Model Catalog Connector in relation to RHDH release cycles. As there is a bit of disconnect between the OpenShift AI release cycle and RHDH release

Background/Feature Origin

As the Model Catalog Connector matures, there is a need to perform regular maintenance on the component on a recurring basis. The plugin pieces are currently covered under our regular plugin maintenance effort RHIDP-11582, however the sidecar service has the OpenShift AI dependency we will need to patch regularly as well, but we first need to investigate if patching OpenShift AI will fit into the RHDH release cycle schedule or will it need to be handled separately going forward.

Why is this important?

To complete our maintenance obligations to the Model Catalog Connector, we have to determine a suitable maintenance schedule for patching the OpenShift AI dependency.

User Scenarios

Dependencies (internal and external)

Acceptance Criteria

Find a suitable maintenance schedule for patching the OpenShift AI dependency
Perform the OpenShift AI v3 patch to best determine the scope and regular maintenance need