You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/container-registry/container-registry-artifact-streaming.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,7 +48,7 @@ Artifact streaming is currently in preview. The following limitations apply:
48
48
* The preview release doesn't support Windows-based container images, and ARM64 images.
49
49
* The preview release partially support multi-architecture images, only the AMD64 architecture is supported.
50
50
* For creating Ubuntu based node pool in AKS, choose Ubuntu version 20.04 or higher.
51
-
* For Kubernetes, use Kubernetes version 1.26 or higher or k8s version > 1.25.
51
+
* For Kubernetes, use Kubernetes version 1.26 or higher or Kubernetes version > 1.25.
52
52
* 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.
53
53
* The CMK (Customer-Managed Keys) registries are NOT supported in the preview release.
54
54
* Kubernetes regcred is currently NOT supported.
@@ -163,7 +163,7 @@ Follow the steps to create artifact streaming in the [Azure portal](https://port
163
163
4. Convert the image and create artifact streaming in Azure portal.
164
164
165
165
> [!div class="mx-imgBorder"]
166
-
> [](./media/container-registry-artifact-streaming/01-create-artifact-streaming-expanded.png#lightbox)
166
+
> [](./media/container-registry-artifact-streaming/01-create-artifact-streaming-expanded.png#lightbox)
167
167
168
168
169
169
5. Check the streaming artifact generated from the image in Referrers tab.
@@ -174,12 +174,12 @@ Follow the steps to create artifact streaming in the [Azure portal](https://port
174
174
6. You can also delete the artifact streaming from the repository blade.
175
175
176
176
> [!div class="mx-imgBorder"]
177
-
> [](./media/container-registry-artifact-streaming/04-delete-artifact-streaming-expanded.png#lightbox)
177
+
> [](./media/container-registry-artifact-streaming/04-delete-artifact-streaming-expanded.png#lightbox)
178
178
179
179
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.
180
180
181
181
> [!div class="mx-imgBorder"]
182
-
> [](./media/container-registry-artifact-streaming/03-start-artifact-streaming-expanded.png#lightbox)
182
+
> [](./media/container-registry-artifact-streaming/03-start-artifact-streaming-expanded.png#lightbox)
183
183
184
184
> [!NOTE]
185
185
> 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.
0 commit comments