You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/app-service/manage-create-arc-environment.md
+11-9Lines changed: 11 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: msangapu-msft
5
5
ms.author: msangapu
6
6
ms.topic: article
7
7
ms.custom: devx-track-azurecli
8
-
ms.date: 03/24/2023
8
+
ms.date: 09/23/2024
9
9
---
10
10
# Set up an Azure Arc-enabled Kubernetes cluster to run App Service, Functions, and Logic Apps (Preview)
11
11
@@ -17,6 +17,8 @@ Azure Arc-enabled Kubernetes lets you make your on-premises or cloud Kubernetes
17
17
18
18
If you don't have an Azure account, [sign up today](https://azure.microsoft.com/free/?utm_source=campaign&utm_campaign=vscode-tutorial-app-service-extension&mktingSource=vscode-tutorial-app-service-extension) for a free account.
19
19
20
+
Review the [requirements and limitations](overview-arc-integration.md) of the public preview. Of particular importance are the cluster requirements.
21
+
20
22
<!-- ## Prerequisites
21
23
22
24
- Create a Kubernetes cluster in a supported Kubernetes distribution and connect it to Azure Arc in a supported region. See [Public preview limitations](overview-arc-integration.md#public-preview-limitations).
> This tutorial uses [Azure Kubernetes Service (AKS)](/azure/aks/) to provide concrete instructions for setting up an environment from scratch. However, for a production workload, you will likely not want to enable Azure Arc on an AKS cluster as it is already managed in Azure. The steps below will help you get started understanding the service, but for production deployments, they should be viewed as illustrative, not prescriptive. See [Quickstart: Connect an existing Kubernetes cluster to Azure Arc](/azure/azure-arc/kubernetes/quickstart-connect-cluster) for general instructions on creating an Azure Arc-enabled Kubernetes cluster.
61
+
> This tutorial uses [Azure Kubernetes Service (AKS)](/azure/aks/) to provide concrete instructions for setting up an environment from scratch. However, for a production workload, you will likely not want to enable Azure Arc on an AKS cluster as it is already managed in Azure. The steps will help you get started understanding the service, but for production deployments, they should be viewed as illustrative, not prescriptive. See [Quickstart: Connect an existing Kubernetes cluster to Azure Arc](/azure/azure-arc/kubernetes/quickstart-connect-cluster) for general instructions on creating an Azure Arc-enabled Kubernetes cluster.
60
62
61
63
1. Create a cluster in Azure Kubernetes Service with a public IP address. Replace `<group-name>` with the resource group name you want.
62
64
@@ -207,7 +209,7 @@ While a [Log Analytic workspace](/azure/azure-monitor/logs/quick-create-workspac
207
209
208
210
## Install the App Service extension
209
211
210
-
1. Set the following environment variables for the desired name of the [App Service extension](overview-arc-integration.md), the cluster namespace in which resources should be provisioned, and the name for the App Service Kubernetes environment. Choose a unique name for `<kube-environment-name>`, because it will be part of the domain name for app created in the App Service Kubernetes environment.
212
+
1. Set the following environment variables for the desired name of the [App Service extension](overview-arc-integration.md), the cluster namespace in which resources should be provisioned, and the name for the App Service Kubernetes environment. Choose a unique name for `<kube-environment-name>`, because it is part of the domain name for app created in the App Service Kubernetes environment.
211
213
212
214
# [bash](#tab/bash)
213
215
@@ -291,13 +293,13 @@ While a [Log Analytic workspace](/azure/azure-monitor/logs/quick-create-workspac
291
293
292
294
| Parameter | Description |
293
295
| - | - |
294
-
| `Microsoft.CustomLocation.ServiceAccount` | The service account that should be created for the custom location that will be created. It is recommended that this be set to the value `default`. |
296
+
| `Microsoft.CustomLocation.ServiceAccount` | The service account that should be created for the custom location that is created. It is recommended that this be set to the value `default`. |
295
297
| `appsNamespace` | The namespace to provision the app definitions and pods. **Must** match that of the extension release namespace. |
296
-
| `clusterName` | The name of the App Service Kubernetes environment that will be created against this extension. |
298
+
| `clusterName` | The name of the App Service Kubernetes environment that is created against this extension. |
297
299
| `keda.enabled` | Whether [KEDA](https://keda.sh/) should be installed on the Kubernetes cluster. Accepts `true` or `false`. |
298
-
| `buildService.storageClassName` | The [name of the storage class](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#class) for the build service to store build artifacts. A value like `default` specifies a class named `default`, and not [any class that is marked as default](https://kubernetes.io/docs/tasks/administer-cluster/change-default-storage-class/). Default is a valid storage class for AKS and AKS HCI but it may not be for other distrubtions/platforms. |
299
-
| `buildService.storageAccessMode` | The [access mode](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes) to use with the named storage class above. Accepts `ReadWriteOnce` or `ReadWriteMany`. |
300
-
| `customConfigMap` | The name of the config map that will be set by the App Service Kubernetes environment. Currently, it must be `<namespace>/kube-environment-config`, replacing `<namespace>` with the value of `appsNamespace` above. |
300
+
| `buildService.storageClassName` | The [name of the storage class](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#class) for the build service to store build artifacts. A value like `default` specifies a class named `default`, and not [any class that is marked as default](https://kubernetes.io/docs/tasks/administer-cluster/change-default-storage-class/). Default is a valid storage class for AKS and AKS HCI but it may not be for other distrubtions/platforms. |
301
+
| `buildService.storageAccessMode` | The [access mode](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes) to use with the named storage class. Accepts `ReadWriteOnce` or `ReadWriteMany`. |
302
+
| `customConfigMap` | The name of the config map that will be set by the App Service Kubernetes environment. Currently, it must be `<namespace>/kube-environment-config`, replacing `<namespace>` with the value of `appsNamespace`. |
301
303
| `envoy.annotations.service.beta.kubernetes.io/azure-load-balancer-resource-group` | The name of the resource group in which the Azure Kubernetes Service cluster resides. Valid and required only when the underlying cluster is Azure Kubernetes Service. |
| `logProcessor.appLogs.logAnalyticsConfig.customerId` | Required only when `logProcessor.appLogs.destination` is set to `log-analytics`. The base64-encoded Log analytics workspace ID. This parameter should be configured as a protected setting. |
@@ -338,7 +340,7 @@ While a [Log Analytic workspace](/azure/azure-monitor/logs/quick-create-workspac
338
340
az resource wait --ids $EXTENSION_ID --custom "properties.installState!='Pending'" --api-version "2020-07-01-preview"
339
341
```
340
342
341
-
You can use `kubectl` to see the pods that have been created in your Kubernetes cluster:
343
+
You can use `kubectl` to see the pods created in your Kubernetes cluster:
| Supported Azure regions | East US, West Europe |
32
32
| Cluster networking requirement | Must support `LoadBalancer` service type |
33
+
| Node OS requirement |**Linux** only. |
33
34
| Cluster storage requirement | Must have cluster attached storage class available for use by the extension to support deployment and build of code-based apps where applicable |
34
35
| Feature: Networking |[Not available (rely on cluster networking)](#are-all-networking-features-supported)|
@@ -68,6 +69,7 @@ Only one Kubernetes environment resource can be created in a custom location. In
68
69
69
70
-[How much does it cost?](#how-much-does-it-cost)
70
71
-[Are both Windows and Linux apps supported?](#are-both-windows-and-linux-apps-supported)
72
+
-[Can the extension be installed on Windows nodes?](#can-the-extension-be-installed-on-windows-nodes)
71
73
-[Which built-in application stacks are supported?](#which-built-in-application-stacks-are-supported)
72
74
-[Are all app deployment types supported?](#are-all-app-deployment-types-supported)
73
75
-[Which App Service features are supported?](#which-app-service-features-are-supported)
@@ -76,7 +78,7 @@ Only one Kubernetes environment resource can be created in a custom location. In
76
78
-[Are there any scaling limits?](#are-there-any-scaling-limits)
77
79
-[What logs are collected?](#what-logs-are-collected)
78
80
-[What do I do if I see a provider registration error?](#what-do-i-do-if-i-see-a-provider-registration-error)
79
-
-[Can I deploy the Application services extension on an ARM64 based cluster?](#can-i-deploy-the-application-services-extension-on-an-arm64-based-cluster)
81
+
-[Can I deploy the Application services extension on an Arm64 based cluster?](#can-i-deploy-the-application-services-extension-on-an-arm64-based-cluster)
80
82
-[Which Kubernetes distributions can I deploy the extension on?](#which-kubernetes-distributions-can-i-deploy-the-extension-on)
81
83
82
84
### How much does it cost?
@@ -87,6 +89,10 @@ App Service on Azure Arc is free during the public preview.
87
89
88
90
Only Linux-based apps are supported, both code and custom containers. Windows apps aren't supported.
89
91
92
+
### Can the extension be installed on Windows nodes?
93
+
94
+
No, the extension cannot be installed on Windows nodes. The extension supports installation on **Linux** nodes **only**.
95
+
90
96
### Which built-in application stacks are supported?
91
97
92
98
All built-in Linux stacks are supported.
@@ -119,11 +125,11 @@ By default, logs from system components are sent to the Azure team. Application
119
125
120
126
### What do I do if I see a provider registration error?
121
127
122
-
When creating a Kubernetes environment resource, some subscriptions might see a "No registered resource provider found" error. The error details might include a set of locations and api versions that are considered valid. If this error message is returned, the subscription must be re-registered with the Microsoft.Web provider, an operation that has no impact on existing applications or APIs. To re-register, use the Azure CLI to run `az provider register --namespace Microsoft.Web --wait`. Then reattempt the Kubernetes environment command.
128
+
When creating a Kubernetes environment resource, some subscriptions might see a "No registered resource provider found" error. The error details might include a set of locations and API versions that are considered valid. If this error message is returned, the subscription must be re-registered with the Microsoft.Web provider, an operation that has no impact on existing applications or APIs. To re-register, use the Azure CLI to run `az provider register --namespace Microsoft.Web --wait`. Then reattempt the Kubernetes environment command.
123
129
124
-
### Can I deploy the Application services extension on an ARM64 based cluster?
130
+
### Can I deploy the Application services extension on an Arm64 based cluster?
125
131
126
-
ARM64 based clusters aren't supported at this time.
132
+
Arm64 based clusters aren't supported at this time.
127
133
128
134
### Which Kubernetes distributions can I deploy the extension on?
Copy file name to clipboardExpand all lines: articles/azure-functions/durable/durable-functions-storage-providers.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ The key benefits of the Azure Storage provider include:
30
30
* Lowest-cost serverless billing model - Azure Storage has a consumption-based pricing model based entirely on usage ([more information](durable-functions-billing.md#azure-storage-transactions)).
31
31
* Best tooling support - Azure Storage offers cross-platform local emulation and integrates with Visual Studio, Visual Studio Code, and the Azure Functions Core Tools.
32
32
* Most mature - Azure Storage was the original and most battle-tested storage backend for Durable Functions.
33
-
*Preview support for using identity instead of secrets for connecting to the storage provider.
33
+
*Support for using identity instead of secrets for connecting to the storage provider.
34
34
35
35
The source code for the DTFx components of the Azure Storage storage provider can be found in the [Azure/durabletask](https://github.com/Azure/durabletask/tree/main/src/DurableTask.AzureStorage) GitHub repo.
| Core capabilities | Join Teams meeting via URL | ✔️ |
21
-
|| Join Teams meeting via meeting ID & passcode | ✔️ |
20
+
| Core capabilities | Join Teams for Work meeting [7] via URL | ✔️ |
21
+
|| Join Teams for Work meeting [7] via meeting ID & passcode | ✔️ |
22
+
|| Join Teams for Home meeting [7]| ❌ |
22
23
|| Join [end-to-end encrypted Teams meeting](/microsoftteams/teams-end-to-end-encryption)| ❌ |
23
24
|| Join channel Teams meeting | ✔️ [1]|
24
25
|| Join Teams [webinars](/microsoftteams/plan-webinars)| ❌ |
@@ -206,6 +207,7 @@ This article describes which capabilities Azure Communication Services SDKs supp
206
207
1. The Communication Services calling SDK doesn't receive a signal that a user is admitted and waiting for the meeting to start. The UI library doesn't support chat while waiting for the meeting to start.
207
208
1. The Communication Services chat SDK shows the real identity of attendees.
208
209
1. Functionality isn't available for users who aren't part of the organization.
210
+
1. If you are using Microsoft 365 work and school account then you use Teams for Work. If you schedule a meeting with this identity, the meeting's URL ends with `teams.microsoft.com`. If you are using personal account then you use Teams for Home. If you schedule a meeting with this identity, the meeting's URL ends with `teams.live.com`. Learn more about those accounts in our [documentation](https://support.microsoft.com/account-billing/what-s-the-difference-between-a-microsoft-account-and-a-work-or-school-account-72f10e1e-cab8-4950-a8da-7c45339575b0).
Copy file name to clipboardExpand all lines: articles/container-apps/azure-arc-enable-cluster.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,6 +36,7 @@ This tutorial will show you how to enable Azure Container Apps on your Arc-enabl
36
36
- If you don't have one, you [can create one for free](https://azure.microsoft.com/free/).
37
37
- Install the [Azure CLI](/cli/azure/install-azure-cli).
38
38
- Access to a public or private container registry, such as the [Azure Container Registry](/azure/container-registry/).
39
+
- Review the [requirements and limitations](azure-arc-overview.md) of the public preview. Of particular importance are the cluster requirements.
39
40
40
41
## Setup
41
42
@@ -253,6 +254,9 @@ A [Log Analytics workspace](/azure/azure-monitor/logs/quick-create-workspace) pr
253
254
254
255
## Install the Container Apps extension
255
256
257
+
> [!IMPORTANT]
258
+
> If deploying onto **AKS-HCI** ensure that you have [setup HAProxy as your load balancer](/azure/aks/hybrid/configure-load-balancer) before attempting to install the extension.
259
+
256
260
1. Set the following environment variables to the desired name of the [Container Apps extension](azure-arc-create-container-app.md), the cluster namespace in which resources should be provisioned, and the name for the Azure Container Apps connected environment. Choose a unique name for `<connected-environment-name>`. The connected environment name will be part of the domain name for app you'll create in the Azure Container Apps connected environment.
0 commit comments