Konflux components in acm and mce use release plan admissions to promote images to acm-d.  For external teams that build on konflux the same thing happens, it's just the external team owns the RPA and they work with our build team so acm-d can be updated.

There is a 3rd case which involves some external images that are shared or not built by ACM or one of our associated product development teams.  An example is the postgresql image.  These images also need to exist in acm-d so our teams can load them from a single internal registry – which is apparently what our QE team does today.

The full list of images that we currently know about that fall into this category are:

ACM:

• configmap_reloader
• origin_cli
• redis_7
• postgresql_16
• memcached

Source that points to ACM images is: https://github.com/stolostron/acm-operator-bundle/blob/27f3d5d7d0e91524f16feb8a47a7de5efd9455ba/config/acm-manifest-gen-config.json#L55

MCE:

• ose_cluster_api_rhel9
• ose_aws_cluster_api_controllers_rhel9
• ose_baremetal_cluster_api_controllers_rhel9
• postgresql_12

Source that points to MCE images is: https://github.com/stolostron/mce-operator-bundle/blob/0f0f08b55d960b2caeaab17bd598f6a201735a44/config/mce-manifest-gen-config.json#L37