Prefix catalog name created by mirror_ocp to avoid clashes with prior OpenShift installations

[ChrisSchneiderIBM]

I installed OpenShift using oc-mirror and also mirrored the LVM-Operator. Therefore I already created a redhat/certified-operator-index image.

When I installed Maximo, the container images used for the mirror_ocp catalogs overwrite the "original" container image.

Therefore it would be great if the container images behind the catalogs created by mirror_ocp would be prefixed with ibm, e.g. instead of an image named redhat/certified-operator-index create an image prefixed with ibm-mas

[durera]

We can provide an option to customise the catalog names when using our code to set up the red hat catalogs, but generally speeaking if there's already a certified-operator-index catalog source there shouldn't be a need to set up one with our roles.

[ChrisSchneiderIBM]

@durera: Thank you for your response!

While there is already a certified-operator-index catalog source, it does not mirror the full catalog to reduce size. Re-using the catalog from the MAS Ansible Role would allow us to rely on the MAS Ansible role to specify dependencies & versioning

[lokesh-sreedhara]

@ChrisSchneiderIBM had a internal chat with David, here is how you can solve this.

In this case you don’t need to use mirror ocp. We can’t just name them something different, it’s still clashes. There are 2 options:

• manage the red hat catalogs yourself
• OR use the mas cli to manage them

We would recommend MAS CLI to manage the OCP and MAS catalogs

[ChrisSchneiderIBM]

Thank you for your response @lokesh-sreedhara. Is there a way in MAS CLI to add my own operators, like OpenShift Update Service, RHACM, Logging etc?

Managing the RH catalogs required by Maximo myself comes with the challenge that I've to manually keep them in sync with MAS CLI.

For now I worked around the issue by giving my separately mirrored catalog a different name:

ocp_mirror_operators:
- catalog: registry.redhat.io/redhat/redhat-operator-index:v{{ ocp_version }}
  targetCatalog: redhat2/redhat-operator-index
  packages:
    ...

[durera]

Action here should be:

• new parameter in https://github.com/ibm-mas/ansible-devops/tree/b8cd290493651529ac0a85117e6d5ec5c588dbab/ibm/mas_devops/roles/ocp_contentsourcepolicy redhat_catalogs_prefix
• use this prefix in the catalog source names: https://github.com/ibm-mas/ansible-devops/blob/b8cd290493651529ac0a85117e6d5ec5c588dbab/ibm/mas_devops/roles/ocp_contentsourcepolicy/templates/redhat-catalogs.yml.j2
• prefix should default to nothing, resulting in no change of behaviour/making sure this isn't a breaking change

Should be straightforward change to make and test by just running the role in isolation and checking the catalogsources, doesn't matter if the catalog sources are pointing at something that even exists for the purpose of this test.