Skip to content

Commit 955779e

Browse files
edits
1 parent 11d6d94 commit 955779e

File tree

2 files changed

+10
-1
lines changed

2 files changed

+10
-1
lines changed

articles/azure-arc/kubernetes/extensions-release.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -213,6 +213,15 @@ For more information, see [Try Azure AI Video Indexer enabled by Arc](/azure/azu
213213

214214
For more information, see [What is Edge Storage Accelerator?](../edge-storage-accelerator/overview.md).
215215

216+
## Connected registry Arc extension
217+
218+
- **Supported distributions**: Connected registry Arc extension using the CLI UX with secure-by-default settings.
219+
- **Supported Azure regions**: All regions where Azure Arc-enabled Kubernetes is available.
220+
221+
The connected registry extension for Azure Arc enables you to sync container images between your Azure Container Registry (ACR) and your Azure Arc-enabled Kubernetes cluster. The extension is deployed to the cluster and uses a synchronization schedule and window to sync images between the connected registry and the cloud registry.
222+
223+
For more information, see [Secure and deploy connected registry Arc extension](../../container-registry/quickstart-connected-registry-arc-cli.md).
224+
216225
## Next steps
217226

218227
- Read more about [cluster extensions for Azure Arc-enabled Kubernetes](conceptual-extensions.md).

articles/container-registry/quickstart-connected-registry-arc-cli.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ The connected registry is a pivotal tool for edge customers, enabling efficient
5454
5555
## Deploy the connected registry Arc extension with secure-by-default settings
5656
57-
Once the prerequisites and necessary conditions and components are in place, follow the streamlined approach to securely deploy a connected registry extension on an Arc-enabled Kubernetescluster using the following settings. These settings define the following configuration with HTTPS, Read Only, Trust Distribution, and Cert Manager service. Follow the steps for a successful deployment:
57+
Once the prerequisites and necessary conditions and components are in place, follow the streamlined approach to securely deploy a connected registry extension on an Arc-enabled Kubernetes cluster using the following settings. These settings define the following configuration with HTTPS, Read Only, Trust Distribution, and Cert Manager service. Follow the steps for a successful deployment:
5858
5959
1. [Create the connected registry.](#create-the-connected-registry-and-synchronize-with-acr)
6060
2. [Deploy the connected registry Arc extension.](#deploy-the-connected-registry-arc-extension-on-the-arc-enabled-kubernetes-cluster)

0 commit comments

Comments
 (0)