Skip to content

Commit 6b8bae4

Browse files
committed
Updates
1 parent ed48e41 commit 6b8bae4

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

articles/reliability/reliability-container-instances.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ All containers in a container group are deployed together as a single logical un
4242

4343
The following diagram shows the relationship between container groups, containers, and images.
4444

45-
:::image type="complex" border="false" source="media/reliability-container-instances/container-groups-containers.svg" alt-text="Diagram that shows a container group with two containers. Each container uses a separate image in a registry." lightbox="media/reliability-container-instances/container-groups-containers.svg":::
45+
:::image type="complex" border="false" source="media/reliability-container-instances/container-groups-containers.svg" alt-text="Diagram that shows a container group with two containers. Each container uses a separate image in a registry.":::
4646
The image shows two containers within a container group section. Two dotted lines connect the containers to two image sections in the registry section.
4747
:::image-end:::
4848

@@ -72,7 +72,7 @@ Container Instances supports availability zones in different ways, depending on
7272

7373
- **Manually created container groups:** An individual container group is a *zonal* resource, which means that it can be deployed into a single availability zone that you select. All containers within the group are deployed into the same availability zone. If that availability zone has an outage, the container group and all of its containers might experience downtime.
7474

75-
:::image type="complex" border="false" source="media/reliability-container-instances/container-groups-containers-zonal.svg" alt-text="Diagram that shows a container group with two containers deployed into a single availability zone" lightbox="media/reliability-container-instances/container-groups-containers-zonal.svg":::
75+
:::image type="complex" border="false" source="media/reliability-container-instances/container-groups-containers-zonal.svg" alt-text="Diagram that shows a container group with two containers deployed into a single availability zone":::
7676
The image shows three availability zones: Availability Zone 1, Availability Zone 2, and Availability Zone 3. A container group in Availability Zone 1 includes two containers.
7777
:::image-end:::
7878

@@ -83,7 +83,7 @@ Container Instances supports availability zones in different ways, depending on
8383

8484
- **NGroups:** When you deploy an NGroup, you can specify one or more zones to deploy it to. If you deploy an NGroup to two or more zones, it's a *zone-redundant* NGroup, and an outage of one availability zone only causes problems for the container groups within the affected zone.
8585

86-
:::image type="complex" border="false" source="media/reliability-container-instances/ngroup-zone-redundant.svg" alt-text="Diagram that shows an NGroup with three container groups, deployed into three availability zones." lightbox="media/reliability-container-instances/ngroup-zone-redundant.svg":::
86+
:::image type="complex" border="false" source="media/reliability-container-instances/ngroup-zone-redundant.svg" alt-text="Diagram that shows an NGroup with three container groups, deployed into three availability zones.":::
8787
The image shows three availability zones. Each availability zone includes a container group and two containers. A rectangle labeled NGroupdesiredCount=3, zones=1,2,3 spans all three availability zones.
8888
:::image-end:::
8989

0 commit comments

Comments
 (0)