Need to determine if the following applies to our use case:

Special Instructions for OperatorHub (IIB) Distribution

First, see the first point above; you shouldn't need this unless your operator is exceptional. But if you do:

You are shipping your operator through the marketplace/OperatorHub if it is not one of the operators shipped through the CVO (cluster version operator).

ART automation handles most of the transformations that PnT DevOps asks you to follow in this document:

• Red Hat Operators - Productization

We do need you to do a few more things in your source repository in order for us to handle this.

1. In the directory containing your operator manifests, include a package.yaml and art.yaml somewhat like local-storage.
2. For the items that need to be included in your operator bundle (including the CSV file), create a subdirectory and place them there (again like local-storage - however note that it no longer needs to be the version in 4.6+, and shouldn't be).
3. In that subdir also provide a list of images that the operator manages (again like local-storage).

Feel free to move on to Request Addition to ART Build System (below) while you are setting up your repository with the necessary changes.