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-private-link.md
+10-12Lines changed: 10 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Set up private link
3
3
description: Set up a private endpoint on a container registry and enable a private link in a local virtual network
4
4
ms.topic: article
5
-
ms.date: 03/07/2020
5
+
ms.date: 03/10/2020
6
6
---
7
7
8
8
# Configure Azure Private Link for an Azure container registry
@@ -19,7 +19,7 @@ This feature is available in the **Premium** container registry service tier. Fo
19
19
20
20
## Prerequisites
21
21
22
-
* To use the Azure CLI steps in this article, Azure CLI version 2.1.1 or later is recommended. If you need to install or upgrade, see [Install Azure CLI][azure-cli]. Or run in [Azure Cloud Shell](../cloud-shell/quickstart.md).
22
+
* To use the Azure CLI steps in this article, Azure CLI version 2.2.0 or later is recommended. If you need to install or upgrade, see [Install Azure CLI][azure-cli]. Or run in [Azure Cloud Shell](../cloud-shell/quickstart.md).
23
23
* If you don't already have a container registry, create one (Premium tier required) and push a sample image such as `hello-world` from Docker Hub. For example, use the [Azure portal][quickstart-portal] or the [Azure CLI][quickstart-cli] to create a registry.
24
24
25
25
The Azure CLI examples in this article use the following environment variables. Substitute values appropriate for your environment. All examples are formatted for the Bash shell:
@@ -240,14 +240,6 @@ az network private-dns record-set a add-record \
240
240
241
241
The private link is now configured and ready for use.
242
242
243
-
To show details of a registry's private endpoint connection, run the [az acr private-endpoint-connection show][az-acr-private-endpoint-connection-show] command. For example:
The following steps assume you already have a virtual network and subnet set up with a VM for testing. You can also [create a new virtual network and subnet](../virtual-network/quick-create-portal.md).
@@ -351,7 +343,13 @@ Docker successfully pulls the image to the VM.
351
343
352
344
Manage a registry's private endpoint connections using the Azure portal, or by using commands in the [az acr private-endpoint-connection][az-acr-private-endpoint-connection] command group. Operations include approve, delete, list, reject, or show details of a registry's private endpoint connections.
353
345
354
-
By default when you create a private endpoint connection, the registry automatically accepts connections from clients and services that have RBAC permissions on the registry. You can set up the endpoint to require manual approval of connections. For information about approving and rejecting private endpoint connections, see [Manage a Private Endpoint Connection](../private-link/manage-private-endpoint.md).
346
+
For example, to list the private endpoint connections of a registry, run the [az acr private-endpoint-connection list][az-acr-private-endpoint-connection-list] command. For example:
347
+
348
+
```azurecli
349
+
az acr private-endpoint-connection list \
350
+
--registry-name $registryName
351
+
352
+
When you set up a private endpoint connection using the steps in this article, the registry automatically accepts connections from clients and services that have RBAC permissions on the registry. You can set up the endpoint to require manual approval of connections. For information about how to approve and reject private endpoint connections, see [Manage a Private Endpoint Connection](../private-link/manage-private-endpoint.md).
355
353
356
354
## Clean up resources
357
355
@@ -384,7 +382,7 @@ To clean up your resources in the portal, navigate to your resource group. Once
0 commit comments