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
+42-36Lines changed: 42 additions & 36 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: What is a Connected Registry
2
+
title: What is a Connected Registry?
3
3
description: Overview and scenarios of the Connected Registry feature of Azure Container Registry, including its benefits and use cases.
4
4
ms.author: jeburke
5
5
ms.service: container-registry
@@ -13,36 +13,47 @@ ms.custom: references_regions
13
13
14
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
-
> [!IMPORTANT]
17
-
> 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).
16
+
## Billing and Support
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).
19
+
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.
22
+
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.
26
+
- This fee represents Microsoft's commitment to deliver high-quality services and product support.
27
+
- The fee will be applied to the Azure subscription associated with the parent registry.
28
+
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.
32
+
- Microsoft advises users to begin planning their transition to Arc-enabled Kubernetes clusters as the deployment model.
18
33
19
34
## Available regions
20
35
21
-
Connected registry is supported in following regions:
22
-
23
-
| Continent | Region |
24
-
|--------------|------------------|
25
-
| East Asia | Japan |
26
-
|| Southeast Asia |
27
-
|||
28
-
| North America| Canada Central |
29
-
|| Canada Central |
30
-
|| East US |
31
-
|| East US 2 EUAP |
32
-
|| South Central US |
33
-
|| West Central US |
34
-
|| West US |
35
-
|| West US 3 |
36
-
|||
37
-
| Europe | Norway East |
38
-
|| North Europe |
39
-
|| West Europe |
40
-
|||
41
-
| Oceania | Australia East |
42
-
|||
43
-
| Middle East | UAE |
44
-
|||
45
-
| South America| Brazil South |
36
+
Connected registry is available in the following continents and regions:
37
+
38
+
```markdown
39
+
| Continent | Available Regions |
40
+
|---------------|-------------------|
41
+
| Australia | Australia East |
42
+
| Asia | East Asia |
43
+
| | Japan East |
44
+
| | Japan West |
45
+
| | Southeast Asia |
46
+
| Europe | North Europe |
47
+
| | Norway East |
48
+
| | West Europe |
49
+
| North America | Canada Central |
50
+
| | Central US |
51
+
| | East US |
52
+
| | South Central US |
53
+
| | West Central US |
54
+
| | West US 3 |
55
+
| South America | Brazil South |
56
+
```
46
57
47
58
## Scenarios
48
59
@@ -65,7 +76,7 @@ The connected registry is deployed on a server or device on-premises, or an envi
65
76
66
77
The following image shows a typical deployment model for the connected registry using IoT Edge.
67
78
68
-
:::image type="content" source="media/intro-connected-registry/connected-registry-overview.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":::
69
80
70
81
The following image shows a typical deployment model for the connected registry using Azure Arc-enabled Kubernetes.
71
82
@@ -102,7 +113,7 @@ A connected registry can work in one of two modes: *ReadWrite* or *ReadOnly*
102
113
103
114
### Registry hierarchy
104
115
105
-
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.md) 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.
106
117
107
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.
108
119
@@ -132,16 +143,11 @@ For more information, see [Manage access to a connected registry][overview-conne
132
143
-`minSyncWindow` is 1 hr
133
144
-`maxSyncWindow` is 7 days
134
145
135
-
## Next steps
146
+
## Conclusion
136
147
137
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