Skip to content

Commit 5a05d61

Browse files
authored
Update get-started-with-cluster-registry.md
1 parent 89f08f2 commit 5a05d61

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
@@ -43,7 +43,7 @@ When the cluster registry feature is enabled in the Network Function Operator Ar
4343
## Frequently Asked Questions
4444

4545
### Can I use AOSM cluster registry with a CNF application previously deployed?
46-
If there's a CNF application already installed using AOSM on a Nexus Kubernetes cluster, and the AOSM cluster registry feature is turned on, the cluster registry doesn't not have the container images automatically. To use this feature, the cluster registry should be turned on before deploying the network function with AOSM.
46+
If there's a CNF application already deployed without cluster registry, the container images are not available automatically. The cluster registry must be enabled before deploying the network function with AOSM.
4747

4848
### Which Nexus K8s storage class is used?
4949
AOSM cluster registry feature uses nexus-volume storage class to store the container images in the Nexus Kubernetes cluster. By default, a 100-GB persistent volume is created if the user doesn't specify the size of the cluster registry.

0 commit comments

Comments
 (0)