Assign an Artifact Registry to an Environment

This section will walk through how to assign an Artifact Registry to an Environment. To deploy containers that exist from an external OCI registry to an Environment, you must first assign the corresponding Artifact Registry to the Environment. This will allow the agents in the Environment to pull images from the Artifact Registry and deploy them.

Step 1: Navigate to the Environment Artifact Registry settings

Navigate to the Environment, then under the Settings tab, select the Artifact Registry tab. This will display a list of Artifact Registries that have been assigned to the Environment. This list will remain empty until you assign at least one Artifact Registry.

Step 2: Assign the Artifact Registry to the Environment

Select Add Artifact Registry to assign a new Artifact Registry to the Environment. This will display a list of all Artifact Registries that have been created in Apollo. Note that you can add or remove as many Artifact Registries as you would like, and all changes will be submitted at once when you select Submit.

Once submitted, a change request will be created. This change request will require an approval from a user in a team that has the "Assigner" RBAC role. Once approved, the Artifact Registry will be assigned to the Environment.

Step 3: Ensure changes have been propagated to the Environment

Once approved, you can check the progress of the Artifact Registry assignment in the Activity tab of the Environment. This will show the installation, change version, and uninstall Plans for Artifact Registries.

Once the install Plan has completed, you can view the connection status of the Artifact Registry, both on the Environment overview page widget and in the Artifact Registries tab in your Hub settings. The connection status will transition from "Pending" to "Connected" when the Artifact Registry has been successfully assigned to the Environment. At this point, you can install Products that rely on this Artifact Registry to the Environment.