Skip to content

Commit f85ce0f

Browse files
authored
Merge pull request #181531 from cebundy/fix-container-app-terminology-2
change files with ref to container apps
2 parents 7715d81 + 6f8b63d commit f85ce0f

7 files changed

+8
-8
lines changed

articles/confidential-computing/confidential-containers.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,9 +14,9 @@ ms.custom: ignite-fall-2021
1414

1515
Azure confidential computing offers confidential containers. There are multiple [options you can choose for confidential containers](choose-confidential-containers-offerings.md). Secured and isolated environments with attestation, improve the overall security of your container deployments.
1616

17-
A hardware-based Trusted Execution Environment (TEE) provides strong assurances. A TEE provides hardware and software measurements from trusted computing base (TCB) components. Confidential containers offerings on Azure allow verification of these measurements and validate if the container apps run in a verifiable execution environment.
17+
A hardware-based Trusted Execution Environment (TEE) provides strong assurances. A TEE provides hardware and software measurements from trusted computing base (TCB) components. Confidential containers offerings on Azure allow verification of these measurements and validate if the container applications run in a verifiable execution environment.
1818

19-
Confidential containers support custom applications developed with any programming languages. You can also run Docker container apps off the shelf.
19+
Confidential containers support custom applications developed with any programming languages. You can also run Docker containers off the shelf.
2020

2121
:::image type="content" source="./media/confidential-containers/sgx-confidential-container.png" alt-text="Diagram of confidential container protection boundary in Kubernetes, showing no access for admins.":::
2222

articles/container-instances/container-instances-container-group-ssl.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ You set up an example container group consisting of two containers:
1212
* An application container that runs a simple web app using the public Microsoft [aci-helloworld](https://hub.docker.com/_/microsoft-azuredocs-aci-helloworld) image.
1313
* A sidecar container running the public [Nginx](https://hub.docker.com/_/nginx) image, configured to use TLS.
1414

15-
In this example, the container group only exposes port 443 for Nginx with its public IP address. Nginx routes HTTPS requests to the companion web app, which listens internally on port 80. You can adapt the example for container apps that listen on other ports.
15+
In this example, the container group only exposes port 443 for Nginx with its public IP address. Nginx routes HTTPS requests to the companion web app, which listens internally on port 80. You can adapt the example for container applications that listen on other ports.
1616

1717
See [Next steps](#next-steps) for other approaches to enabling TLS in a container group.
1818

articles/container-instances/container-instances-gpu.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Deploy GPU-enabled container instance
3-
description: Learn how to deploy Azure container instances to run compute-intensive container apps using GPU resources.
3+
description: Learn how to deploy Azure container instances to run compute-intensive container applications using GPU resources.
44
ms.topic: article
55
ms.date: 07/22/2020
66
---

articles/container-instances/container-instances-image-security.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.custom:
88

99
# Security considerations for Azure Container Instances
1010

11-
This article introduces security considerations for using Azure Container Instances to run container apps. Topics include:
11+
This article introduces security considerations for using Azure Container Instances to run container applications. Topics include:
1212

1313
> [!div class="checklist"]
1414
> * **Security recommendations** for managing images and secrets for Azure Container Instances

articles/container-instances/container-instances-readiness-probe.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.date: 07/02/2020
77

88
# Configure readiness probes
99

10-
For containerized applications that serve traffic, you might want to verify that your container is ready to handle incoming requests. Azure Container Instances supports readiness probes to include configurations so that your container can't be accessed under certain conditions. The readiness probe behaves like a [Kubernetes readiness probe](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/). For example, a container app might need to load a large data set during startup, and you don't want it to receive requests during this time.
10+
For containerized applications that serve traffic, you might want to verify that your container is ready to handle incoming requests. Azure Container Instances supports readiness probes to include configurations so that your container can't be accessed under certain conditions. The readiness probe behaves like a [Kubernetes readiness probe](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/). For example, a container application might need to load a large data set during startup, and you don't want it to receive requests during this time.
1111

1212
This article explains how to deploy a container group that includes a readiness probe, so that a container only receives traffic when the probe succeeds.
1313

articles/container-instances/container-instances-troubleshooting.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -209,7 +209,7 @@ If you want to confirm that Azure Container Instances can listen on the port you
209209
--environment-variables 'PORT'='9000'
210210
```
211211
1. Find the IP address of the container group in the command output of `az container create`. Look for the value of **ip**.
212-
1. After the container is provisioned successfully, browse to the IP address and port of the container app in your browser, for example: `192.0.2.0:9000`.
212+
1. After the container is provisioned successfully, browse to the IP address and port of the container application in your browser, for example: `192.0.2.0:9000`.
213213
214214
You should see the "Welcome to Azure Container Instances!" message displayed by the web app.
215215
1. When you're done with the container, remove it using the `az container delete` command:

articles/container-instances/container-instances-tutorial-deploy-app.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Tutorial - Deploy container app to container instance
2+
title: Tutorial - Deploy container application to container instance
33
description: Azure Container Instances tutorial part 3 of 3 - Deploy container application to Azure Container Instances
44
ms.topic: tutorial
55
ms.date: 03/21/2018

0 commit comments

Comments
 (0)