About private registries with Edge

Updated: June 5, 2025

A private container image registry allows you to use your own infrastructure to perform security scans and audit container images consumed by your Edge site. Before you configure a private container registry, keep the following in mind:

Switching to a private container image registry is only possible during installation. If you want to add a private container image registry for an existing Edge site, you need to reinstall your Edge site with your registry.
All Edge site container images must live in the same registry.
When copying images to your private container image registry, make sure only the domain name is updated when tagging the new images.

Note

Custom Helm registries are not supported.
Other forms of security scanning, such as penetration tests, can be performed either independently or as a part of the security flow that includes a private container image registry.
Security scan reports are only accepted for supported Edge versions. This is because security fixes are not applied to old, out-dated versions of Edge. For example, from November 19, 2023 to February 24, 2024, security scans are only accepted for Edge version 2023.11 and subsequent weekly updates (2023.11.x). For information on which Edge versions are supported with the latest release, go to the Compatibility between Edge and Collibra Data Intelligence Cloud.

Supported private container image registries

Note The above list shows the tested and supported private container image registries. If your private container image registry is not listed but uses user/pass authentication, you can attempt to install your Edge site with your registry. However, Collibra Support can't provide assistance for untested registries.