RFE: Extend it to be able to consume more than one index image at the same time

[tiraboschi]

Now we have an index image for each OCP release and we are releasing some .z versions of our project only to a specific OCP index image.
For our project we really care about the upgrade path across OCP upgrades so I think we should add the capability to audit at the same time more than one index image from different OCP releases.

[camilamacedo86]

Hi @tiraboschi,

That seems very interesting. However, before we came with a design solution and its implementation would be great we be able to identify what we need to check across the index. So, could you help us by providing some criteria? For example, what are the common issues that can happen which we could check validate in this scenario? What info would be helpful to obtain across the index?

[camilamacedo86]

The catalogue custom report is using the data from many indexes now. See: https://github.com/operator-framework/audit/tree/main/cmd/custom/catalogs

So, I think that we could try to do something similar here to generate custom reports to:

Check migration paths and availability in the upper versions and report issues only

Use Case

I would like to have a friendly dashboard(s) highlighting the problems that need to be addressed to provide a better user experience and avoid issues. So, I can quickly and automatically/programmatically identify what the teams need to do to address them.

Where, for example: 
 

• Shows relevant info to avoid issues when the users upgrade their cluster from OCP version N to N+1:  
• Not distributed in the upper version (e.g. if we found the project on 4. N but it does not exist in 4.N+1) 
• Not have a valid upgrade path and will not be able to get updates (e.g. if I have the operator version Y installed and upgrade the cluster will result in breaking its updates)
• Missing the dependencies (e.g. the operator A depend on B and C, but B and C are not available in the upper version)

To allow us to check all distributions for many indexes informed

E.g., we show all bundles and channels and, if possible, upgrade paths for all indexes from many indexes informed.