Skip to content

Commit 69f50ff

Browse files
authored
Merge pull request Azure#637 from Azure/canary
Canary
2 parents ea77905 + 345e23b commit 69f50ff

File tree

13 files changed

+10
-27
lines changed

13 files changed

+10
-27
lines changed
Loading
Loading
Loading
Loading
Loading
Loading
Loading
Loading
Loading
Loading
Loading

docs/azure_arc_jumpstart/azure_arc_app_svc/aks/aks_container_apps_arm_template/_index.md

+10-27
Original file line numberDiff line numberDiff line change
@@ -16,11 +16,7 @@ By the end of this scenario, you will have an Azure Kubernetes Service (AKS) clu
1616
1717
The following Jumpstart scenario will guide you on how to run cloud-native application on [Azure Container Apps](https://azure.microsoft.com/products/container-apps/). The Azure Container Apps service enables you to run microservices and containerized applications on a serverless platform. Individual container apps are deployed to a single Container Apps environment, which acts as a secure boundary around groups of container apps.
1818

19-
In this scenario, you will deploy a [Container Apps environment](https://learn.microsoft.com/azure/container-apps/environment) and a 3-node container app running in Azure. The app leverages [Dapr](https://learn.microsoft.com/azure/container-apps/dapr-overview?tabs=bicep1%2Cyaml) to simplify service to service invocation.
20-
21-
- Store - The store app is simulating the store's frontend app by running the [Quickstart sample application](https://learn.microsoft.com/azure/container-apps/get-started) in a container.
22-
- Products API - This is simulating an API application by running the [Quickstart sample application](https://learn.microsoft.com/azure/container-apps/get-started) in a container.
23-
- Inventory API - A simulation of an API application running the [Quickstart sample application](https://learn.microsoft.com/azure/container-apps/get-started) in a container.
19+
In this scenario, you will deploy a [Container Apps environment](https://learn.microsoft.com/azure/container-apps/environment) and a 'Hello World' container [app](https://learn.microsoft.com/azure/container-apps/get-started) running in Azure.
2420

2521
## Prerequisites
2622

@@ -111,11 +107,6 @@ As mentioned, this deployment will leverage ARM templates. You will deploy a sin
111107
- _`windowsAdminUsername`_ - Client Windows VM Administrator username
112108
- _`windowsAdminPassword`_ - Client Windows VM Password. Password must have 3 of the following: 1 lower case character, 1 upper case character, 1 number, and 1 special character. The value must be between 12 and 123 characters long.
113109
- _`logAnalyticsWorkspaceName`_ - Unique name for the deployment log analytics workspace.
114-
- _`deployContainerApps`_ - Boolean that sets whether or not to deploy Azure Container Apps environment and a Web App. For this scenario, we leave it set to *`true`*.
115-
- _`deployAppService`_ - Boolean that sets whether or not to deploy App Service plan and a Web App. For this scenario, we leave it set to *`false`*.
116-
- _`deployFunction`_ - Boolean that sets whether or not to deploy App Service plan and an Azure Function application. For this scenario, we leave it set to *`false`*.
117-
- _`deployAPIMgmt`_ - Boolean that sets whether or not to deploy a self-hosted Azure API Management gateway. For this scenario, we leave it set to *`false`*.
118-
- _`deployLogicApp`_ - Boolean that sets whether or not to deploy App Service plan and an Azure Logic App. For this scenario, we leave it set to *`false`*.
119110
- _`templateBaseUrl`_ - GitHub URL to the deployment template - filled in by default to point to [Microsoft/Azure Arc](https://aka.ms/JumpstartGitHubCode) repository, but you can point this to your forked repo as well.
120111
- _`deployBastion`_ - Choice (true | false) to deploy [Azure Bastion](https://learn.microsoft.com/azure/bastion/bastion-overview) or not to connect to the client VM.
121112
- _`bastionHostName`_ - Azure Bastion host name.
@@ -219,10 +210,6 @@ If you already have [Microsoft Defender for Cloud](https://learn.microsoft.com/a
219210

220211
![Screenshot showing PowerShell logon script run](./16.png)
221212

222-
![Screenshot showing PowerShell logon script run](./17.png)
223-
224-
![Screenshot showing PowerShell logon script run](./18.png)
225-
226213
Once the script finishes it's run, the logon script PowerShell session will be closed, the Windows wallpaper will change, and the Azure Container Apps deployed on the cluster will be ready.
227214
228215
![Screenshot showing desktop wallpaper change](./19.png)
@@ -239,27 +226,25 @@ If you already have [Microsoft Defender for Cloud](https://learn.microsoft.com/a
239226

240227
![Screenshot showing additional Azure resources in the resource group](./20.png)
241228

242-
- In this scenario, a **[Quickstart sample application](https://learn.microsoft.com/azure/container-apps/get-started)** was deployed to simulate **Front-end and 2 Back-end APIs on Azure Container Apps**. To open the deployed [Quickstart sample application](https://learn.microsoft.com/azure/container-apps/get-started) in your web browser, simply click the Container App resource and the Application URL.
229+
- In this scenario, a 'Hello World' **[app](https://learn.microsoft.com/azure/container-apps/get-started)** was deployed as a container app. To open the deployed 'Hello World' [app](https://learn.microsoft.com/azure/container-apps/get-started) in your web browser, simply click the Container App resource and the Application URL.
243230

244-
![Screenshot showing Store Container App in a resource group](./21.png)
231+
![Screenshot showing Hello World Container App in a resource group](./21.png)
245232

246233
![Screenshot showing the web application URL](./22.png)
247234

248235
![Screenshot showing the web application open in a web browser](./23.png)
249236

250-
- Optionally, you can review the [Dapr](https://learn.microsoft.com/azure/container-apps/dapr-overview?tabs=bicep1%2Cyaml) configuration for the Container apps by navigating to the Dapr setting.
251-
252-
![Screenshot showing Store Container App Dapr](./24.png)
253-
254237
## Cluster extensions
255238

256239
In this scenario, the Azure Container Apps extension was deployed and used throughout this scenario in order to deploy the Azure Container Apps infrastructure.
257240

258241
- In order to view cluster extensions, click on the Azure Arc-enabled Kubernetes resource Extensions settings.
259242

260-
![Screenshot showing the Azure Arc-enabled Kubernetes resource](./25.png)
243+
![Screenshot showing the Azure Arc-enabled Kubernetes resource](./24.png)
244+
245+
![Screenshot showing Azure Arc-enabled Kubernetes cluster extensions settings](./25.png)
261246

262-
![Screenshot showing Azure Arc-enabled Kubernetes cluster extensions settings](./26.png)
247+
![Screenshot showing Azure Arc-enabled Kubernetes cluster extensions](./26.png)
263248

264249
## View your application's diagnostics
265250

@@ -276,17 +261,15 @@ In this scenario, the Log Analytics was configured with the Container Apps exten
276261
let EndTime = now();
277262
ContainerAppConsoleLogs_CL
278263
| where TimeGenerated between (StartTime .. EndTime)
279-
| where ContainerAppName_s =~ "store"
264+
| where ContainerAppName_s =~ "helloworld"
280265
```
281266
282-
![Screenshot showing showing the Log Analytics workspace logs](./28.png)
283-
284-
![Screenshot showing showing the Log Analytics workspace logs query](./29.png)
267+
![Screenshot showing showing the Log Analytics workspace logs query](./28.png)
285268
286269
> **Note:** If there's an error when running a query, try again in 10-15 minutes. There may be a delay for Log Analytics to start receiving logs from the application.
287270

288271
## Cleanup
289272

290273
- If you want to delete the entire environment, simply delete the deployed resource group from the Azure portal.
291274

292-
![Screenshot showing the Delete Azure resource group button](./30.png)
275+
![Screenshot showing the Delete Azure resource group button](./29.png)

0 commit comments

Comments
 (0)