Skip to content

Commit b626fb2

Browse files
committed
content review
1 parent a3a58cd commit b626fb2

File tree

3 files changed

+16
-17
lines changed

3 files changed

+16
-17
lines changed

articles/reliability/TOC.yml

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -84,11 +84,7 @@
8484
- name: Azure Container Instances
8585
href: reliability-containers.md
8686
- name: Azure Container Registry
87-
items:
88-
- name: Availability zones
89-
href: /azure/container-registry/zone-redundancy?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json
90-
- name: Disaster recovery
91-
href: /azure/container-registry/container-registry-geo-replication?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json
87+
href: reliability-container-registry.md
9288
- name: Azure Kubernetes Service (AKS)
9389
href: reliability-aks.md
9490
- name: Azure Service Fabric

articles/reliability/overview-reliability-guidance.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ This section provides links to reliability guidance for many Azure services. Eac
5353
|Azure Communications Gateway | | [Reliability in Azure Communications Gateway](../communications-gateway/reliability-communications-gateway.md?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json)|
5454
|Azure Container Apps| [Reliability in Azure Container Apps](reliability-azure-container-apps.md)||
5555
|Azure Container Instances| [Reliability in Azure Container Instances](reliability-containers.md)||
56-
|Azure Container Registry||[Enable zone redundancy in Azure Container Registry for resiliency and high availability](/azure/container-registry/zone-redundancy?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json) </p> [Geo-replication in Azure Container Registry](/azure/container-registry/container-registry-geo-replication) |
56+
|Azure Container Registry|[Reliability in Azure Container Registry](reliability-container-registry.md) ||
5757
|Azure Cosmos DB for NoSQL| [Reliability in Azure Cosmos DB for NoSQL](reliability-cosmos-db-nosql.md) ||
5858
|Azure Cosmos DB for MongoDB vCore| [Reliability in Azure Cosmos DB for MongoDB vCore](reliability-cosmos-mongodb.md)||
5959
|Azure Cosmos DB for PostgreSQL| | [Availability zone outage resiliency in Azure Cosmos DB for PostgreSQL](/azure/cosmos-db/postgresql/concepts-availability-zones?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json) </p> [High availability in Azure Cosmos DB for PostgreSQL](/azure/cosmos-db/postgresql/concepts-high-availability?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json)|

articles/reliability/reliability-container-registry.md

Lines changed: 14 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -16,26 +16,17 @@ This article describes reliability support in Azure Container Registry (ACR), co
1616

1717
Azure Container Registry is a managed container registry service used to store and manage your private Docker container images and related artifacts for your container deployments. For more information, see [What is Azure Container Registry?](/azure/container-registry/container-registry-intro).
1818

19-
## Shared responsibility
20-
<!-- Anastasia: What do you think about this section? It's not in our template. Leaving it to you to work out what to do with it. -->
21-
2219
[!INCLUDE [Shared responsibility](includes/reliability-shared-responsibility-include.md)]
2320

24-
Microsoft manages the underlying Azure Container Registry infrastructure, including maintaining the control plane for registry management and the data plane for container image operations across regions and availability zones.
25-
26-
As a customer, you're responsible for:
27-
28-
- **Application-level resilience**: Implementing appropriate retry logic and failover handling in your container applications and orchestration platforms.
29-
- **Zone redundancy configuration**: Enabling zone redundancy for regions where your container registry is deployed or replicated.
30-
- **Geo-replication configuration**: Selecting appropriate regions for geo-replication based on your geographic distribution, compliance, and performance requirements.
31-
3221
## Production deployment recommendations
3322

3423
For production workloads, we recommend that you:
24+
3525
- Use the Premium tier of Azure Container Registry, which provides the most comprehensive reliability features. The Premium tier also provides higher performance limits, enhanced security features, and advanced capabilities that are essential for production container workloads. For complete information on service tiers and features, see [Azure Container Registry service tiers](/azure/container-registry/container-registry-skus).
3626
- Enable zone redundancy to protect against zone-level failures within a region.
3727
- For multi-region scenarios, configure geo-replication to distribute your registry across multiple regions based on your specific geographic and compliance requirements.
3828

29+
3930
## Reliability architecture overview
4031

4132
Azure Container Registry is built on Azure's distributed infrastructure to provide high availability and data durability. The service consists of several key components that work together to ensure reliability. The following diagram illustrates the core service architecture:
@@ -46,11 +37,23 @@ Azure Container Registry is built on Azure's distributed infrastructure to provi
4637
- **Data plane**: Distributed service that handles container image push and pull operations across regions and availability zones
4738
- **Storage layer**: Content-addressable Azure Storage to persist container images and artifacts, with automatic deduplication, encryption at rest, and built-in replication
4839

40+
Microsoft is responsible for managing the underlying Azure Container Registry infrastructure, which includes:
41+
- *Control plane maintenance* for registry management.
42+
- *Data plane maintenance* for container image operations across regions and availability zones.
43+
44+
As a customer, you're responsible for:
45+
46+
- *Application-level resilience*: Implementing appropriate retry logic and failover handling in your container applications and orchestration platforms
47+
- *Zonal-resiliency configuration*: Selecting to enable zone redundancy for regions where your container registry is deployed.
48+
- *Geo-replication configuration*: Selecting appropriate regions for geo-replication based on your geographic distribution, compliance, and performance requirements
49+
4950
Azure Container Registry also supports *tasks*, which can help you to automate your container builds and maintenance operations. Tasks run on compute infrastructure managed by Microsoft, and can be triggered to run manually, based on events, or based on a schedule. To learn more, see [Automate container image builds and maintenance with Azure Container Registry tasks](/azure/container-registry/container-registry-tasks-overview).
5051

5152
> [!NOTE]
5253
> Azure Container Registry supports [connected registries](/azure/container-registry/intro-connected-registry), which are on-premises or remote replicas that synchronize with your cloud-based Azure container registry. When you use connected registries, you're responsible for configuring them to meet your reliability requirements. Connected registries are beyond the scope of this article.
5354
55+
56+
5457
## Transient faults
5558

5659
[!INCLUDE [Transient fault description](includes/reliability-transient-fault-description-include.md)]

0 commit comments

Comments
 (0)