Skip to content

Commit bea4594

Browse files
committed
add to TOC; x-link
1 parent 9a00ab8 commit bea4594

File tree

2 files changed

+4
-2
lines changed

2 files changed

+4
-2
lines changed

articles/container-instances/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -51,6 +51,8 @@
5151
href: container-instances-orchestrator-relationship.md
5252
- name: Security considerations
5353
href: container-instances-image-security.md
54+
- name: Virtual network considerations
55+
href: container-instances-virtual-network-concepts.md
5456
- name: How-to guides
5557
items:
5658
- name: Deploy

articles/container-instances/container-instances-container-groups.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ In this scenario, you could set a resource limit of 2 CPUs for the container ins
6161

6262
## Networking
6363

64-
Container groups can share an external-facing IP address, one or more ports on that IP address, and a DNS label with a fully qualified domain name (FQDN). To enable external clients to reach a container within the group, you must expose the port on the IP address and from the container. Because containers within the group share a port namespace, port mapping isn't supported. A container group's IP address and FQDN will be released when the container group is deleted.
64+
Container groups can share an external-facing IP address, one or more ports on that IP address, and a DNS label with a fully qualified domain name (FQDN). To enable external clients to reach a container within the group, you must expose the port on the IP address and from the container. A container group's IP address and FQDN are released when the container group is deleted.
6565

6666
Within a container group, container instances can reach each other via localhost on any port, even if those ports aren't exposed externally on the group's IP address or from the container.
6767

@@ -110,7 +110,7 @@ Learn how to deploy a multi-container container group with an Azure Resource Man
110110
[resource-limits]: /rest/api/container-instances/containergroups/createorupdate#resourcelimits
111111
[resource-requirements]: /rest/api/container-instances/containergroups/createorupdate#resourcerequirements
112112
[azure-files]: container-instances-volume-azure-files.md
113-
[virtual-network]: container-instances-vnet.md
113+
[virtual-network]: container-instances-virtual-network-concepts.md
114114
[secret]: container-instances-volume-secret.md
115115
[volume-gitrepo]: container-instances-volume-gitrepo.md
116116
[gpus]: container-instances-gpu.md

0 commit comments

Comments
 (0)