Feature Overview (aka. Goal Summary)  

Spike for operator dependencies viewing and mirroring.

Goals (aka. expected user outcomes)

Consider an optimal solution between OLM v1, oc-mirror v2 and ODF (and other operators with dependencies) that will allow smooth deployment of operators in disconnected environments from a first attempt.

This can be a visual viewer for the operators available in the catalog to allow customers view and select dependencies for mirroring. Ideally it should be a solution that skips the requirement of the user to browse operators for dependencies and simply mirror everything needed for a selected operator.

Background

`oc-mirror v2` does not discover operator dependencies anymore compared to v1. Docs

However, this presumes a big challenge for the customers in disconnected environments, since there is no way for the user to know ahead of time that an operator may have a dependencies at the time of mirroring. The missing dependencies are only discovered at the time of install, which creates a very frustrating day 1 installation experience for our customers. Consider this process already taking days and weeks in the first place, this is not an experience we want for our disconnected installations.

There are only few operators that have dependencies, however those operators are heavily used by our disconnected customers, that's why this functionality is important. ODF is number one operator being impacted here.

This OCPSTRAT should be considered alongside OCPSTRAT-2406. 

Requirements (aka. Acceptance Criteria):

• This is a spike. We should work with the mentioned teams to figure out most optimal solution for our users.

Documentation Considerations

N/A