As today, catalogs are provided to the fleet manager in the form of a set of config map which are copied from the catalog repos to the fleet manager before doing a release.

In addition of using configmaps to distribute the connector definitions, we can use container images and an init container to pre-populate an ephemeral volume on the fleet shard:

This allows:

• to avoid creating an additional OpenShift Template and reduces the complexity of configuring the fleet manager as you don't need to add new volumes mount and related flags to the manager each time a catalog is added/removed
• track what catalogs are deployed as they are identified by a container image
• automatically provide PR to update the cos-fleet-manager manifests when a catalog is tagged (similar to what we do for the fleet shard):