Merge pull request #267465 from tejaswikolli-web/Artifact-streaming

American-Dipper · web-flow · commit 1a2a4fd8b086 · 2024-02-27T13:59:00.000-08:00
edits
diff --git a/articles/container-registry/container-registry-artifact-streaming.md b/articles/container-registry/container-registry-artifact-streaming.md
@@ -2,12 +2,13 @@
 title: "Artifact streaming in Azure Container Registry (Preview)"
 description: "Artifact streaming is a feature in Azure Container Registry to enhance and supercharge managing, scaling, and deploying artifacts through containerized platforms."
 author: tejaswikolli-web
-ms.author: tejaswikolli
 ms.service: container-registry
-ms.custom: devx-track-azurecli
+zone_pivot_groups: container-registry-zones
 ms.topic: conceptual #Don't change
-ms.date: 12/14/2023
-# Customer intent: As a developer, I want artifact streaming capabilities so that I can efficiently deliver and serve containerized applications to end-users in real-time.
+ms.date: 02/26/2024
+ai-usage: ai-assisted
+
+#customer intent: As a developer, I want artifact streaming capabilities so that I can efficiently deliver and serve containerized applications to end-users in real-time.
 ---
 
 # Artifact streaming in Azure Container Registry (Preview)
@@ -18,9 +19,9 @@ Artifact streaming is a feature in Azure Container Registry that allows you to s
 
 Here are few scenarios to use artifact streaming:
 
-**Deploying containerized applications to multiple regions**: With artifact streaming, you can store container images within a single registry and manage and stream container images to AKS clusters in multiple regions. artifact streaming deploys container applications to multiple regions without consuming time and resources.
+**Deploying containerized applications to multiple regions**: With artifact streaming, you can store container images within a single registry and manage and stream container images to AKS clusters in multiple regions. Artifact streaming deploys container applications to multiple regions without consuming time and resources.
 
-**Reducing image pull latency**: Artifact streaming can reduce time to pod readiness by over 15%, depending on the size of the image, and it works best for images < 30GB. This feature reduces image pull latency and fast container startup, which is beneficial for software developers and system architects.
+**Reducing image pull latency**: Artifact streaming can reduce time to pod readiness by over 15%, depending on the size of the image, and it works best for images < 30 GB. This feature reduces image pull latency and fast container startup, which is beneficial for software developers and system architects.
 
 **Effective scaling of containerized applications**:  Artifact streaming provides the opportunity to design, build, and deploy containerized applications at a high scale.
 
@@ -30,39 +31,44 @@ Here are some brief aspects of artifact streaming:
 
 * Customers with new and existing registries can start artifact streaming for specific repositories or tags.
 
-* Once artifact streaming is started, the original and the streaming artifact will be stored in the customer’s ACR.
+* Customers are able to store both the original and the streaming artifact in the ACR by starting artifact streaming.
 
-* If the user decides to turn off artifact streaming for repositories or artifacts, the streaming and the original artifact will still be present.
+* Customers have access to the original and the streaming artifact even after turning off artifact streaming for repositories or artifacts.
 
-* If a customer deletes a repository or artifact with artifact streaming and Soft Delete enabled, then both the original and artifact streaming versions will be deleted. However, only the original version will be available on the soft delete blade.
+* Customers with artifact streaming and Soft Delete enabled, deletes a repository or artifact then both the original and artifact streaming versions are deleted. However, only the original version is available on the soft delete portal.
 
 ## Availability and pricing information
 
-Artifact streaming is only available in the **Premium** SKU [service tiers](container-registry-skus.md). Please note that artifact streaming may increase the overall registry storage consumption and customers may be subjected to additional storage charges as outlined in our [pricing](https://azure.microsoft.com/pricing/details/container-registry/) if the consumption exceeds the included 500 GiB Premium SKU threshold.
+Artifact streaming is only available in the **Premium** [service tiers](container-registry-skus.md) (also known as SKUs). Artifact streaming has potential to increase the overall registry storage consumption. Customers are subjected to more storage charges as outlined in our [pricing](https://azure.microsoft.com/pricing/details/container-registry/) if the consumption exceeds the included 500 GiB Premium SKU threshold.
 
 ## Preview limitations
 
 Artifact streaming is currently in preview. The following limitations apply:
 
 * Only images with Linux AMD64 architecture are supported in the preview release.
-* The preview release doesn't support Windows-based container images, and ARM64 images.
-* The preview release partially support multi-architecture images, only the AMD64 architecture is supported.
+* The preview release doesn't support Windows-based container images and ARM64 images.
+* The preview release partially support multi-architecture images only the AMD64 architecture is supported.
 * For creating Ubuntu based node pool in AKS, choose Ubuntu version 20.04 or higher.
 * For Kubernetes, use Kubernetes version 1.26 or higher or Kubernetes version > 1.25. 
-* Only premium SKU registries support generating streaming artifacts in the preview release. The non-premium SKU registries do not offer this functionality during the preview.
+* Only premium SKU registries support generating streaming artifacts in the preview release. The nonpremium SKU registries don't offer this functionality during the preview.
 * The CMK (Customer-Managed Keys) registries are NOT supported in the preview release.
 * Kubernetes regcred is currently NOT supported.
 
 ## Prerequisites
 
-* You can use the [Azure Cloud Shell][Azure Cloud Shell] or a local installation of the Azure CLI to run the command examples in this article. If you'd like to use it locally, version 2.54.0 or later is required. Run `az --version` to find the version. If you need to install or upgrade, see [Install Azure CLI][Install Azure CLI].
+* You can use the [Azure Cloud Shell][Azure Cloud Shell] or a local installation of the Azure CLI to run the command examples in this article. If you'd like to use it locally, version 2.54.0 or later is required. Run `az --version` for finding the version. If you need to install or upgrade, see [Install Azure CLI][Install Azure CLI].
 
 * Sign in to the [Azure portal](https://ms.portal.azure.com/). 
 
+
 ## Start artifact streaming 
 
 Start artifact streaming with a series with Azure CLI commands and Azure portal for pushing, importing, and generating streaming artifacts for container images in an Azure Container Registry (ACR). These instructions outline the process for creating a *Premium* [SKU](container-registry-skus.md) ACR, importing an image, generating a streaming artifact, and managing the artifact streaming operation. Make sure to replace the placeholders with your actual values where necessary.
 
+<!-- markdownlint-disable MD044 -->
+:::zone target="docs" pivot="development-environment-azure-cli"
+<!-- markdownlint-enable MD044 -->
+
 ### Push/Import the image and generate the streaming artifact  - Azure CLI
 
 Artifact streaming is available in the **Premium** container registry service tier. To start Artifact streaming, update a registry using the Azure CLI (version 2.54.0 or above). To install or upgrade, see [Install Azure CLI](/cli/azure/install-azure-cli).
@@ -115,22 +121,22 @@ Start artifact streaming, by following these general steps:
 
 5. Cancel the artifact streaming creation (if needed)
 
-    Cancel the streaming artifact creation if the conversion is not finished yet. It will stop the operation.
+    Cancel the streaming artifact creation if the conversion isn't finished yet. It stops the operation.
     
     For example, run the [az acr artifact-streaming operation cancel][az-acr-artifact-streaming-operation-cancel] command to cancel the conversion operation for the `jupyter/all-spark-notebook:latest` image in the `mystreamingtest` ACR.
 
     ```azurecli-interactive
     az acr artifact-streaming operation cancel --repository jupyter/all-spark-notebook --id c015067a-7463-4a5a-9168-3b17dbe42ca3
     ```
 
-6. Start auto-conversion on the repository
+6. Start autoconversion on the repository
 
-    Start auto-conversion in the repository for newly pushed or imported images. When started, new images pushed into that repository will trigger the generation of streaming artifacts.
+    Start autoconversion in the repository for newly pushed or imported images. When started, new images pushed into that repository trigger the generation of streaming artifacts.
 
     >[!NOTE]
     > Auto-conversion does not apply to existing images. Existing images can be manually converted.
     
-    For example, run the [az acr artifact-streaming update][az-acr-artifact-streaming-update] command to start auto-conversion for the `jupyter/all-spark-notebook` repository in the `mystreamingtest` ACR.
+    For example, run the [az acr artifact-streaming update][az-acr-artifact-streaming-update] command to start autoconversion for the `jupyter/all-spark-notebook` repository in the `mystreamingtest` ACR.
 
     ```azurecli-interactive
     az acr artifact-streaming update --repository jupyter/all-spark-notebook --enable-streaming true
@@ -144,10 +150,18 @@ Start artifact streaming, by following these general steps:
     az acr artifact-streaming operation show --image jupyter/all-spark-notebook:newtag
     ```
 
+
+:::zone-end
+
+
 >[!NOTE]
 > Artifact streaming can work across regions, regardless of whether geo-replication is started or not.
 > Artifact streaming can work through a private endpoint and attach to it.
 
+<!-- markdownlint-disable MD044 -->
+:::zone target="docs" pivot="development-environment-azure-portal"
+<!-- markdownlint-enable MD044 -->
+
 ### Push/Import the image and generate the streaming artifact - Azure portal
 
 Artifact streaming is available in the *premium* [SKU](container-registry-skus.md) Azure Container Registry. To start artifact streaming, update a registry using the Azure portal.
@@ -171,23 +185,27 @@ Follow the steps to create artifact streaming in the [Azure portal](https://port
    > [!div class="mx-imgBorder"]
    > [![A screenshot of Azure portal with the streaming artifact highlighted.](./media/container-registry-artifact-streaming/02-artifact-streaming-generated-inline.png)](./media/container-registry-artifact-streaming/02-artifact-streaming-generated-expanded.png#lightbox)
 
-6. You can also delete the artifact streaming from the repository blade. 
+6. You can also delete the artifact streaming from the repository. 
 
    > [!div class="mx-imgBorder"]
    > [![A screenshot of Azure portal with the delete artifact streaming button highlighted.](./media/container-registry-artifact-streaming/04-delete-artifact-streaming-inline.png)](./media/container-registry-artifact-streaming/04-delete-artifact-streaming-expanded.png#lightbox)
 
-7. You can also enable auto-conversion on the repository blade. Active means auto-conversion is enabled on the repository. Inactive means auto-conversion is disabled on the repository. 
+7. You can also enable autoconversion by accessing the repository on portal. Active means autoconversion is enabled on the repository. Inactive means autoconversion is disabled on the repository. 
     
    > [!div class="mx-imgBorder"]
    > [![A screenshot of Azure portal with the start artifact streaming button highlighted.](./media/container-registry-artifact-streaming/03-start-artifact-streaming-inline.png)](./media/container-registry-artifact-streaming/03-start-artifact-streaming-expanded.png#lightbox)
 
 > [!NOTE]
 > The state of artifact streaming in a repository (inactive or active) determines whether newly pushed compatible images will be automatically converted. By default, all repositories are in an inactive state for artifact streaming. This means that when new compatible images are pushed to the repository, artifact streaming will not be triggered, and the images will not be automatically converted. If you want to start automatic conversion of newly pushed images, you need to set the repository's artifact streaming to the active state. Once the repository is in the active state, any new compatible container images that are pushed to the repository will trigger artifact streaming. This will start the automatic conversion of those images.
 
+
+:::zone-end
+
+
 ## Next steps
 
 > [!div class="nextstepaction"]
-> [Troubleshoot artifact streaming](troubleshoot-artifact-streaming.md)
+> [Troubleshoot Artifact streaming](troubleshoot-artifact-streaming.md)
 
 <!-- LINKS - External -->
 [Install Azure CLI]: /cli/azure/install-azure-cli
diff --git a/articles/container-registry/troubleshoot-artifact-streaming.md b/articles/container-registry/troubleshoot-artifact-streaming.md
@@ -1,14 +1,14 @@
 ---
-title: "Troubleshoot artifact streaming"
-description: "Troubleshoot artifact streaming in Azure Container Registry to diagnose and resolve with managing, scaling, and deploying artifacts through containerized platforms."
+title: "Troubleshoot Artifact streaming"
+description: "Troubleshoot Artifact streaming in Azure Container Registry to diagnose and resolve with managing, scaling, and deploying artifacts through containerized platforms."
 ms.author: tejaswikolli
 ms.service: container-registry
 ms.topic: troubleshooting-general #Don't change.
 ms.date: 10/31/2023
 
 ---
 
-# Troubleshoot artifact streaming
+# Troubleshoot Artifact streaming
 
 The troubleshooting steps in this article can help you resolve common issues that you might encounter when using artifact streaming in Azure Container Registry (ACR). These steps and recommendations can help diagnose and resolve issues related to artifact streaming as well as provide insights into the underlying processes and logs for debugging purposes.
 
@@ -17,7 +17,7 @@ The troubleshooting steps in this article can help you resolve common issues tha
 * Conversion operation failed due to an unknown error.
 * Troubleshooting Failed AKS Pod Deployments.
 * Pod conditions indicate "UpgradeIfStreamableDisabled."
-* Using Digest Instead of Tag for Streaming Artifact
+* Digest usage instead of Tag for Streaming Artifact.
 
 ## Causes
 
@@ -30,16 +30,16 @@ The troubleshooting steps in this article can help you resolve common issues tha
 | Error Code                  | Error Message                                                                      | Troubleshooting Info                                                                                                                                                                                                                                      |
 | --------------------------- | ---------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | UNKNOWN_ERROR               | Conversion operation failed due to an unknown error.                               | Caused by an internal error. A retry helps here. If retry is unsuccessful, contact support.                                                                                                                                                                |
-| RESOURCE_NOT_FOUND          | Conversion operation failed because target resource isn't found.                   | If the target image isn't found in the registry. Verify typos in the image digest, if the image is deleted, or missing in the target region (replication consistency is not immediate for example)                                                        |
-| UNSUPPORTED_PLATFORM        | Conversion is not currently supported for image platform.                          | Only linux/amd64 images are initially supported.                                                                                                                                                                                                          |
-| NO_SUPPORTED_PLATFORM_FOUND | Conversion is not currently supported for any of the image platforms in the index. | Only linux/amd64 images are initially supported. No image with this platform is found in the target index.                                                                                                                                                |
-| UNSUPPORTED_MEDIATYPE       | Conversion is not supported for the image MediaType.                               | Conversion can only target images with media type: application/vnd.oci.image.manifest.v1+json, application/vnd.oci.image.index.v1+json, application/vnd.docker.distribution.manifest.v2+json or application/vnd.docker.distribution.manifest.list.v2+json |
+| RESOURCE_NOT_FOUND          | Conversion operation failed because target resource isn't found.                   | If the target image isn't found in the registry, verify typos in the image digest. If the image is deleted, or missing in the target region (replication consistency isn't immediate for example)                                                        |
+| UNSUPPORTED_PLATFORM        | Conversion isn't currently supported for image platform.                          | Only linux/amd64 images are initially supported.                                                                                                                                                                                                          |
+| NO_SUPPORTED_PLATFORM_FOUND | Conversion isn't currently supported for any of the image platforms in the index. | Only linux/amd64 images are initially supported. No image with this platform is found in the target index.                                                                                                                                                |
+| UNSUPPORTED_MEDIATYPE       | Conversion isn't supported for the image MediaType.                               | Conversion can only target images with media type: application/vnd.oci.image.manifest.v1+json, application/vnd.oci.image.index.v1+json, application/vnd.docker.distribution.manifest.v2+json, or application/vnd.docker.distribution.manifest.list.v2+json |
 | UNSUPPORTED_ARTIFACT_TYPE   | Conversion isn't supported for the image ArtifactType.                             | Streaming Artifacts (Artifact type: application/vnd.azure.artifact.streaming.v1) can't be converted again.                                                                                                                                                |
 | IMAGE_NOT_RUNNABLE          | Conversion isn't supported for nonrunnable images.                                 | Only linux/amd64 runnable images are initially supported.                                                                                                                                                                                                 |
 
 ## Troubleshooting Failed AKS Pod Deployments
 
-If AKS pod deployment fails with an error related to image pulling, like the following example
+If AKS pod deployment fails with an error related to image pulling, like the following example.
 
 ```bash
 Failed to pull image "mystreamingtest.azurecr.io/jupyter/all-spark-notebook:latest":
@@ -49,9 +49,9 @@ failed to resolve reference "mystreamingtest.azurecr.io/jupyter/all-spark-notebo
 unexpected status from HEAD request to http://localhost:8578/v2/jupyter/all-spark-notebook/manifests/latest?ns=mystreamingtest.azurecr.io:503 Service Unavailable
 ```
 
-To troubleshoot this issue, you should check the following:
+To troubleshoot this issue, you should check the following guidelines:
 
-1. Verify if the AKS has permissions to access the container registry `mystreamingtest.azurecr.io`
+1. Verify if the AKS has permissions to access the container registry `mystreamingtest.azurecr.io`.
 1. Ensure that the container registry `mystreamingtest.azurecr.io` is accessible and properly attached to AKS.
 
 ## Checking for "UpgradeIfStreamableDisabled" Pod Condition:
diff --git a/articles/zone-pivot-groups.yml b/articles/zone-pivot-groups.yml
