Alauda Container Platform

Registry v2: Operator-Managed ACP Registry

This section describes Registry v2, the Operator-managed Registry deployed and reconciled by cluster-image-registry-operator. Registry v2 follows the same information architecture as the OpenShift Container Platform 4.21 Registry documentation: overview, Image Registry Operator, setting up and configuring the registry, accessing the registry, and exposing the registry. ACP-specific image management and migration content is added as separate pages.

The legacy Registry documentation remains available under How To for environments that still use the earlier cpaas-system Registry service.

TOC

Documentation StructureStandard Addresses

Documentation Structure

OCP 4.21 Registry chapterACP Registry v2 page
OpenShift image registry overviewACP image registry overview
Image Registry Operator in OpenShift Container PlatformImage Registry Operator
Setting up and configuring the registrySetting up and configuring the registry
Accessing the registryAccessing the registry
Exposing the registryExposing the registry
ACP-specific ac image management topicManaging images with ac
ACP-specific migration topicMigrating from the legacy ACP Registry

Standard Addresses

Use the Registry v2 internal service address for workloads running in the cluster:

image-registry.image-registry-system.svc:5000

The short service address can be used for compatibility validation when node DNS and trust configuration support it:

image-registry.image-registry-system:5000

Use an external Ingress hostname for developer machines, CI systems, and other clients outside the cluster.