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/intro-connected-registry.md
+36-36Lines changed: 36 additions & 36 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,29 +6,29 @@ ms.service: container-registry
6
6
ms.topic: overview
7
7
ms.date: 10/31/2023
8
8
ms.custom: references_regions
9
-
#customer intent: As a reader, I want to understand the overview and scenarios of the connected registry feature of Azure Container Registry so that I can utilize it effectively.
9
+
#customer intent: As a reader, I want to understand the overview and scenarios of the Connected registry feature of Azure Container Registry so that I can utilize it effectively.
10
10
---
11
11
12
12
# What is a Connected Registry?
13
13
14
-
In this article, you learn about the *connected registry* feature of [Azure Container Registry](container-registry-intro.md). A connected registry is an on-premises or remote replica that synchronizes container images and other OCI artifacts with your cloud-based Azure container registry. Use a connected registry to help speed up access to registry artifacts on-premises and to build advanced scenarios, for example using [nested IoT Edge](../iot-edge/tutorial-nested-iot-edge.md).
14
+
In this article, you learn about the *Connected registry* feature of [Azure Container Registry](container-registry-intro.md). A Connected registry is an on-premises or remote replica that synchronizes container images and other OCI artifacts with your cloud-based Azure container registry. Use a Connected registry to help speed up access to registry artifacts on-premises and to build advanced scenarios, for example using [nested IoT Edge](../iot-edge/tutorial-nested-iot-edge.md).
15
15
16
16
## Billing and Support
17
17
18
-
The connected registry is a preview feature of the **Premium** container registry service tier, and subject to [limitations](#limitations). For information about registry service tiers and limits, see [Azure Container Registry service tiers](container-registry-skus.md).
18
+
The Connected registry is a preview feature of the **Premium** container registry service tier, and subject to [limitations](#limitations). For information about registry service tiers and limits, see [Azure Container Registry service tiers](container-registry-skus.md).
19
19
20
20
>[!IMPORTANT]
21
-
> Please note that there are **important upcoming changes** to the Connected Registry Deployment Model Support and Billing starting from September 30th, 2024. For any inquiries or assistance with the transition, please reach out to the customer support team.
21
+
> Please note that there are **important upcoming changes** to the Connected registry Deployment Model Support and Billing starting from September 30th, 2024. For any inquiries or assistance with the transition, please reach out to the customer support team.
22
22
23
23
### Billing
24
-
- The Connected Registry will incur no charges until it reaches general availability (GA).
25
-
- Post-GA, a monthly fee of $10 will apply for each connected registry deployed.
24
+
- The Connected registry will incur no charges until it reaches general availability (GA).
25
+
- Post-GA, a monthly fee of $10 will apply for each Connected registry deployed.
26
26
- This fee represents Microsoft's commitment to deliver high-quality services and product support.
27
27
- The fee will be applied to the Azure subscription associated with the parent registry.
28
28
29
29
### Support
30
-
- Microsoft will end support for the Connected Registry deployment on IoT Edge devices on September 30th, 2024.
31
-
- After September 30th, 2024, Connected Registry will solely support Arc-enabled Kubernetes clusters as the deployment model.
30
+
- Microsoft will end support for the Connected registry deployment on IoT Edge devices on September 30th, 2024.
31
+
- After September 30th, 2024, Connected registry will solely support Arc-enabled Kubernetes clusters as the deployment model.
32
32
- Microsoft advises users to begin planning their transition to Arc-enabled Kubernetes clusters as the deployment model.
33
33
34
34
## Available regions
@@ -59,9 +59,9 @@ Connected registry is available in the following continents and regions:
59
59
60
60
A cloud-based Azure container registry provides [features](container-registry-intro.md#key-features) including geo-replication, integrated security, Azure-managed storage, and integration with Azure development and deployment pipelines. At the same time, customers are extending their cloud investments to their on-premises and field solutions.
61
61
62
-
To run with the required performance and reliability in on-premises or remote environments, container workloads need container images and related artifacts to be available nearby. The connected registry provides a performant, on-premises registry solution that regularly synchronizes content with a cloud-based Azure container registry.
62
+
To run with the required performance and reliability in on-premises or remote environments, container workloads need container images and related artifacts to be available nearby. The Connected registry provides a performant, on-premises registry solution that regularly synchronizes content with a cloud-based Azure container registry.
63
63
64
-
Scenarios for a connected registry include:
64
+
Scenarios for a Connected registry include:
65
65
66
66
* Connected factories
67
67
* Point-of-sale retail locations
@@ -70,71 +70,71 @@ Scenarios for a connected registry include:
70
70
* Customize persistent storage volumes for container workloads
71
71
* Secure delivery, tracking, and auto management of updates
72
72
73
-
## How does the connected registry work?
73
+
## How does the Connected registry work?
74
74
75
-
The connected registry is deployed on a server or device on-premises, or an environment that supports container workloads on-premises such as Azure IoT Edge and Azure Arc-enabled Kubernetes. The connected registry synchronizes container images and other OCI artifacts with a cloud-based Azure container registry.
75
+
The Connected registry is deployed on a server or device on-premises, or an environment that supports container workloads on-premises such as Azure IoT Edge and Azure Arc-enabled Kubernetes. The Connected registry synchronizes container images and other OCI artifacts with a cloud-based Azure container registry.
76
76
77
-
The following image shows a typical deployment model for the connected registry using IoT Edge.
77
+
The following image shows a typical deployment model for the Connected registry using IoT Edge.
78
78
79
-
:::image type="content" source="media/intro-connected-registry/connected-registry-edge.png" alt-text="Diagram of connected registry overview using IoT Edge":::
79
+
:::image type="content" source="media/intro-connected-registry/connected-registry-edge.png" alt-text="Diagram of Connected registry overview using IoT Edge":::
80
80
81
-
The following image shows a typical deployment model for the connected registry using Azure Arc-enabled Kubernetes.
81
+
The following image shows a typical deployment model for the Connected registry using Azure Arc-enabled Kubernetes.
82
82
83
-
:::image type="content" source="media/intro-connected-registry/connected-registry-azure-arc.png" alt-text="Diagram of connected registry overview using Arc-enabled Kubernetes":::
83
+
:::image type="content" source="media/intro-connected-registry/connected-registry-azure-arc.png" alt-text="Diagram of Connected registry overview using Arc-enabled Kubernetes":::
84
84
85
85
### Deployment
86
86
87
-
Each connected registry is a resource you manage using a cloud-based Azure container registry. The top parent in the connected registry hierarchy is an Azure container registry in an Azure cloud.
87
+
Each Connected registry is a resource you manage using a cloud-based Azure container registry. The top parent in the Connected registry hierarchy is an Azure container registry in an Azure cloud.
88
88
89
-
Use Azure tools to install the connected registry on a server or device on your premises, or an environment that supports container workloads on-premises such as [Azure IoT Edge](../iot-edge/tutorial-nested-iot-edge.md).
89
+
Use Azure tools to install the Connected registry on a server or device on your premises, or an environment that supports container workloads on-premises such as [Azure IoT Edge](../iot-edge/tutorial-nested-iot-edge.md).
90
90
91
-
Enable connected registry-Arc extension to the Arc-enabled k8s cluster, and securing the connection with TLS with default configurations for Read only and continuous sync window. The connected registry can be deployed on the Arc-enabled k8s cluster and synchronize the images from ACR to connected registry on-perm can be used to pull images from connected registry.
91
+
Enable Connected registry-Arc extension to the Arc-enabled k8s cluster, and securing the connection with TLS with default configurations for Read only and continuous sync window. The Connected registry can be deployed on the Arc-enabled k8s cluster and synchronize the images from ACR to Connected registry on-perm can be used to pull images from Connected registry.
92
92
93
-
The connected registry's *activation status* indicates whether it's deployed on-premises.
93
+
The Connected registry's *activation status* indicates whether it's deployed on-premises.
94
94
95
-
***Active** - The connected registry is currently deployed on-premises. It can't be deployed again until it is deactivated.
96
-
***Inactive** - The connected registry is not deployed on-premises. It can be deployed at this time.
95
+
***Active** - The Connected registry is currently deployed on-premises. It can't be deployed again until it is deactivated.
96
+
***Inactive** - The Connected registry is not deployed on-premises. It can be deployed at this time.
97
97
98
98
### Content synchronization
99
99
100
-
The connected registry regularly accesses the cloud registry to synchronize container images and OCI artifacts.
100
+
The Connected registry regularly accesses the cloud registry to synchronize container images and OCI artifacts.
101
101
102
102
It can also be configured to synchronize a subset of the repositories from the cloud registry or to synchronize only during certain intervals to reduce traffic between the cloud and the premises.
103
103
104
104
### Modes
105
105
106
-
A connected registry can work in one of two modes: *ReadWrite* or *ReadOnly*
106
+
A Connected registry can work in one of two modes: *ReadWrite* or *ReadOnly*
107
107
108
-
-**ReadWrite mode** - The default mode allows clients to pull and push artifacts (read and write) to the connected registry. Artifacts that are pushed to the connected registry will be synchronized with the cloud registry.
108
+
-**ReadWrite mode** - The default mode allows clients to pull and push artifacts (read and write) to the Connected registry. Artifacts that are pushed to the Connected registry will be synchronized with the cloud registry.
109
109
110
-
The ReadWrite mode is useful when a local development environment is in place. The images are pushed to the local connected registry and from there synchronized to the cloud.
110
+
The ReadWrite mode is useful when a local development environment is in place. The images are pushed to the local Connected registry and from there synchronized to the cloud.
111
111
112
-
-**ReadOnly mode** - When the connected registry is in ReadOnly mode, clients can only pull (read) artifacts. This configuration is used for nested IoT Edge scenarios, or other scenarios where clients need to pull a container image to operate.
112
+
-**ReadOnly mode** - When the Connected registry is in ReadOnly mode, clients can only pull (read) artifacts. This configuration is used for nested IoT Edge scenarios, or other scenarios where clients need to pull a container image to operate.
113
113
114
114
### Registry hierarchy
115
115
116
-
Each connected registry must be connected to a parent. The top parent is the cloud registry. For hierarchical scenarios such as [nested IoT Edge][overview-connected-registry-and-iot-edge] and Azure Arc-enabled Kubernetes, you can nest connected registries in either mode. The parent connected to the cloud registry can operate in either mode.
116
+
Each Connected registry must be connected to a parent. The top parent is the cloud registry. For hierarchical scenarios such as [nested IoT Edge][overview-connected-registry-and-iot-edge] and Azure Arc-enabled Kubernetes, you can nest connected registries in either mode. The parent connected to the cloud registry can operate in either mode.
117
117
118
-
Child registries must be compatible with their parent capabilities. Thus, both ReadWrite and ReadOnly mode connected registries can be children of a connected registry operating in ReadWrite mode, but only a ReadOnly mode registry can be a child of a connected registry operating in ReadOnly mode.
118
+
Child registries must be compatible with their parent capabilities. Thus, both ReadWrite and ReadOnly mode connected registries can be children of a Connected registry operating in ReadWrite mode, but only a ReadOnly mode registry can be a child of a Connected registry operating in ReadOnly mode.
119
119
120
120
## Client access
121
121
122
-
On-premises clients use standard tools such as the Docker CLI to push or pull content from a connected registry. To manage client access, you create Azure container registry [tokens][repository-scoped-permissions] for access to each connected registry. You can scope the client tokens for pull or push access to one or more repositories in the registry.
122
+
On-premises clients use standard tools such as the Docker CLI to push or pull content from a Connected registry. To manage client access, you create Azure container registry [tokens][repository-scoped-permissions] for access to each Connected registry. You can scope the client tokens for pull or push access to one or more repositories in the registry.
123
123
124
-
Each connected registry also needs to regularly communicate with its parent registry. For this purpose, the registry is issued a synchronization token (*sync token*) by the cloud registry. This token is used to authenticate with its parent registry for synchronization and management operations.
124
+
Each Connected registry also needs to regularly communicate with its parent registry. For this purpose, the registry is issued a synchronization token (*sync token*) by the cloud registry. This token is used to authenticate with its parent registry for synchronization and management operations.
125
125
126
126
For more information, see [Manage access to a connected registry][overview-connected-registry-access].
127
127
128
128
## Limitations
129
129
130
-
- Number of tokens and scope maps is [limited](container-registry-skus.md) to 20,000 each for a single container registry. This indirectly limits the number of connected registries for a cloud registry, because every connected registry needs a sync and client token.
130
+
- Number of tokens and scope maps is [limited](container-registry-skus.md) to 20,000 each for a single container registry. This indirectly limits the number of connected registries for a cloud registry, because every Connected registry needs a sync and client token.
131
131
- Number of repository permissions in a scope map is limited to 500.
132
-
- Number of clients for the connected registry is currently limited to 20.
132
+
- Number of clients for the Connected registry is currently limited to 20.
133
133
-[Image locking](container-registry-image-lock.md) through repository/manifest/tag metadata is not currently supported for connected registries.
134
-
-[Repository delete](container-registry-delete.md) is not supported on the connected registry using ReadOnly mode.
134
+
-[Repository delete](container-registry-delete.md) is not supported on the Connected registry using ReadOnly mode.
135
135
-[Resource logs](monitor-service-reference.md#resource-logs) for connected registries are currently not supported.
136
136
- Connected registry is coupled with the registry's home region data endpoint. Automatic migration for [geo-replication](container-registry-geo-replication.md) is not supported.
137
-
- Deletion of a connected registry needs manual removal of the containers on-premises as well as removal of the respective scope map or tokens in the cloud.
137
+
- Deletion of a Connected registry needs manual removal of the containers on-premises as well as removal of the respective scope map or tokens in the cloud.
138
138
- Connected registry sync limitations are as follows:
139
139
- For continuous sync:
140
140
-`minMessageTtl` is 1 day
@@ -145,7 +145,7 @@ For more information, see [Manage access to a connected registry][overview-conne
145
145
146
146
## Conclusion
147
147
148
-
In this overview, you learned about the connected registry and some basic concepts. Continue to the one of the following articles to learn about specific scenarios where connected registry can be utilized.
148
+
In this overview, you learned about the Connected registry and some basic concepts. Continue to the one of the following articles to learn about specific scenarios where Connected registry can be utilized.
0 commit comments