Skip to content

Commit 68746be

Browse files
committed
TOC, edits
1 parent 3cb2773 commit 68746be

File tree

3 files changed

+15
-13
lines changed

3 files changed

+15
-13
lines changed

articles/container-registry/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -189,6 +189,8 @@
189189
href: container-registry-tasks-authentication-key-vault.md
190190
- name: Quick task run with Resource Manager template
191191
href: container-registry-task-run-template.md
192+
- name: Run task on dedicated agent pool (preview)
193+
href: container-registry-tasks-agent-pools.md
192194
- name: Build image with Buildpacks (preview)
193195
href: container-registry-tasks-pack-build.md
194196
- name: View task logs

articles/container-registry/container-registry-tasks-agent-pools.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Use dedicated pool to run task - Tasks
3-
description: Use a dedicated compute pool (agent pool) to run an Azure Container Registry task.
3+
description: Set up a dedicated compute pool (agent pool) in your registry to run an Azure Container Registry task.
44
ms.topic: article
55
ms.date: 04/30/2020
66
---
@@ -26,15 +26,14 @@ This feature is available in the **Premium** container registry service tier. Fo
2626

2727
- Task agent pools currently support Linux nodes. Windows nodes are not currently supported.
2828
- Task agent pools are available in preview in the following regions: West US 2, South Central US, East US 2, and East US.
29-
- For each registry, the default total vCPU (core) quota for all agent pools is 16. Please [open a support ticket][open-support-ticket] for additional allocation.
30-
29+
- For each registry, the default total vCPU (core) quota for all agent pools is 16. Open a support ticket][open-support-ticket] for additional allocation.
3130

3231
## Prerequisites
3332

3433
* To use the Azure CLI steps in this article, Azure CLI version 2.3.1 or later is required. If you need to install or upgrade, see [Install Azure CLI][azure-cli]. Or run in [Azure Cloud Shell](../cloud-shell/quickstart.md).
3534
* If you don't already have a container registry, [create one][create-reg-cli](https://docs.microsoft.com/en-us/azure/container-registry/container-registry-get-started-azure-cli) (Premium tier required) in a preview region.
3635

37-
## Pool tiers
36+
## Pool tiers
3837

3938
The following table shows the resources per instance in the agent pool tiers.
4039

@@ -66,7 +65,7 @@ az acr agentpool create \
6665
--tier S2
6766
```
6867

69-
Creating an agent pool and other pool operations can take several minutes to complete.
68+
Creating an agent pool and other pool management operations will take several minutes to complete.
7069

7170
### Scale pool
7271

@@ -99,7 +98,8 @@ Task agent pools require access to the following Azure services. The following f
9998
The following example creates an agent pool in the *mysubnet* subnet of network *myvnet*:
10099

101100
```azurecli
102-
subnet=$(az network vnet subnet show \
101+
# Get the subnet ID
102+
subnetId=$(az network vnet subnet show \
103103
--resource-grop myresourcegroup \
104104
--vnet-name myvnet \
105105
--name mysubnetname \
@@ -108,15 +108,15 @@ subnet=$(az network vnet subnet show \
108108
az acr agentpool create \
109109
--name myagentpool \
110110
--tier S2 \
111-
--subnet-id $subnet
111+
--subnet-id $subnetId
112112
```
113113

114-
## Run tasks on agent pool
114+
## Run task on agent pool
115115

116-
The following sections show how to specify an agent pool when queuing a task.
116+
The following examples show how to specify an agent pool when queuing a task.
117117

118118
> [!NOTE]
119-
> To use an agent pool in an ACR Task, ensure that the pool contains at least 1 instance.
119+
> To use an agent pool in an ACR task, ensure that the pool contains at least 1 instance.
120120
>
121121
122122
### Quick task run
@@ -133,7 +133,7 @@ az acr build \
133133

134134
### Automatically triggered task
135135

136-
For example, create a scheduled task on the agent pool with [az acr task create][az-acr-task-create].
136+
For example, create a scheduled task on the agent pool with [az acr task create][az-acr-task-create], passing the `--agent-pool` parameter.
137137

138138
```azurecli
139139
az acr task create \
@@ -155,7 +155,7 @@ az acr task run \
155155

156156
### Query pool status
157157

158-
Query the agent pool queue status (current scheduled runs on the agent pool) by running [az acr agentpool show][az-acr-agentpool-show].
158+
Query the agent pool queue status (the number of runs currently scheduled on the agent pool) by running [az acr agentpool show][az-acr-agentpool-show].
159159

160160
```azurecli
161161
az acr agentpool show \

articles/container-registry/container-registry-vnet.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ If instead you need to set up access rules for resources to reach a container re
2424

2525
* Only an [Azure Kubernetes Service](../aks/intro-kubernetes.md) cluster or Azure [virtual machine](../virtual-machines/linux/overview.md) can be used as a host to access a container registry in a virtual network. *Other Azure services including Azure Container Instances aren't currently supported.*
2626

27-
* [ACR Tasks](container-registry-tasks-overview.md) operations aren't currently supported in a container registry accessed in a virtual network.
27+
* Running [ACR Tasks](container-registry-tasks-overview.md) in a container registry accessed in a virtual network requires a [dedicated agent pool](container-registry-tasks-agent-pools.md).
2828

2929
* Each registry supports a maximum of 100 virtual network rules.
3030

0 commit comments

Comments
 (0)