Skip to content

Commit 8e5b26a

Browse files
authored
Update get-started-with-cluster-registry.md
1 parent acaa7e4 commit 8e5b26a

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/operator-service-manager/get-started-with-cluster-registry.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ This feature requires the following minimum environment:
2323
* First version, with HA for NF kubernetes extension: 2.0.2810-144
2424
* First version, with GC for NF kubernetes extension: 2.0.2810-144
2525

26-
## Overview
26+
## Cluster registry overview
2727
Azure Operator Service Manager (AOSM) cluster registry (CR) enables a local copy of container images in the Nexus K8s cluster. When the containerized network function (CNF) is installed with cluster registry enabled, the container images are pulled from the remote AOSM artifact store and saved to this local cluster registry. Using a mutating webhook, cluster registry automatically intercepts image requests and substitutes the local registry path, to avoid publisher packaging changes. With cluster register, CNF access to container images survives loss of connectivity to the remote artifact store.
2828

2929
### Key use cases and benefits

0 commit comments

Comments
 (0)