Merge pull request #20 from jordlay/pk5/updates_to_the_help_doc

Update the image upload concepts doc

Author: pjw711

articles/operator-service-manager/concepts-cli-containerized-network-function-image-upload.md

@@ -7,8 +7,8 @@ ms.date: 04/12/2024
 ms.topic: concept-article
 ms.service: azure-operator-service-manager
 ms.custom: devx-track-azurecli
-
 ---
+
 # Learn how the Azure Operator Service Manager (AOSM) CLI extension discovers container images in source ACRs based on helm chart configuration
 
 This document explains how the Azure CLI AOSM extension discovers images in helm charts, pulls them from a container registry, and uploads them to an AOSM Artifact Store. The Azure CLI AOSM extension supports both Azure Container Registry (ACR) and any container registry that supports the Docker API.
@@ -32,8 +32,8 @@ The Az CLI AOSM extension:
 - Searches in the registries and namespaces included in the "image_sources" array for the container image references.
 - Copies the images from the source registries to the AOSM artifact store.
 
->[!IMPORTANT]
->The AOSM CLI requires that the images in your source registry match the namespace structure written in your helm chart. For example, an image included in a helm chart as `core/contoso-a:1.0.0` must be available in the source registry in a path that ends in `core/contoso-a:1.0.0`. Any additional prefix must be included in the `"image_sources"` parameter in the `cnf-input.jsonc` file generated by the `az aosm nfd generate-config --definition-type cnf` command.
+> [!IMPORTANT]
+> The AOSM CLI requires that the images in your source registry match the namespace structure written in your helm chart. For example, an image included in a helm chart as `core/contoso-a:1.0.0` must be available in the source registry in a path that ends in `core/contoso-a:1.0.0`. Any additional prefix must be included in the `"image_sources"` parameter in the `cnf-input.jsonc` file generated by the `az aosm nfd generate-config --definition-type cnf` command.
 
 ## Worked example
 
@@ -51,13 +51,13 @@ The "image_sources" field in the NFDV input file is set as follows:
 The output of `helm template` against the helm charts for this CNF gives four image lines in the Kubernetes deployment definition.
 
 ```yaml
-image: release/contoso-a:1.0.0
-image: release/contoso-b:1.0.0
-image: release/contoso-c:1.0.0
-image: test-release/contoso-test:1.0.0
+image: repository/release/contoso-a:1.0.0
+image: repository/release/contoso-b:1.0.0
+image: repository/release/contoso-c:1.0.0
+image: repository/test-release/contoso-test:1.0.0
 ```
 
-The Azure CLI AOSM extension searches for the images in `myregistry.azurecr.io/release/contoso-a:1.0.0`, `myregistry.azurecr.io/release/contoso-b:1.0.0`, `myregistry.azurecr.io/release/contoso-c:1.0.0`, and `myregistry.azurecr.io/test-release/contoso-test:1.0.0`. The images must be available in these paths.
+The Azure CLI AOSM extension takes in the above image lines and removes the `repository` (AOSM overwrites the repository with the new registry backing the AOSM Artifact Store). Then, the Azure CLI AOSM extension searches for the images in `myregistry.azurecr.io/release/contoso-a:1.0.0`, `myregistry.azurecr.io/release/contoso-b:1.0.0`, `myregistry.azurecr.io/release/contoso-c:1.0.0`, and `myregistry.azurecr.io/test-release/contoso-test:1.0.0`. The images must be available in these paths.
 
 ### Namespacing
 
@@ -74,4 +74,4 @@ The Azure AOSM CLI extension searches for the images in `myregistry.azurecr.io`,
 
 ## Next steps
 
-- [How to onboard a CNF using the CLI](how-to-onboard-containerized-network-function-cli.md)
+- [How to onboard a CNF using the CLI](how-to-onboard-containerized-network-function-cli.md)