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: azure-stack/operator/aks-add-on.md
+16-16Lines changed: 16 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Install and offer the Azure Kubernetes Service on Azure Stack Hub
3
3
description: Learn how to install and offer the Azure Kubernetes Service on Azure Stack Hub.
4
4
author: sethmanheim
5
5
ms.topic: how-to
6
-
ms.date: 04/24/2023
6
+
ms.date: 08/08/2024
7
7
ms.author: sethm
8
8
ms.reviewer: waltero
9
9
ms.lastreviewed: 03/24/2022
@@ -20,11 +20,11 @@ Azure Kubernetes Service (AKS) enables your users to deploy Kubernetes clusters
20
20
To install, you must have the VM extensions, the AKS base image, a plan and offer to your users, and enable multi-tenancy for your Azure Stack Hub. AKS clusters can only be created in the user environment.
21
21
22
22
> [!IMPORTANT]
23
-
> Azure Kubernetes Service on Azure Stack Hub, currently in preview, is being discontinued and will not become GA. See [AKS Engine](../user/azure-stack-kubernetes-aks-engine-overview.md) for a Kubernetes solution on Azure Stack Hub.
23
+
> Azure Kubernetes Service on Azure Stack Hub, currently in preview, is discontinued and won't be released to general availability (GA). See the [AKS Engine overview](../user/azure-stack-kubernetes-aks-engine-overview.md) for a Kubernetes solution on Azure Stack Hub.
24
24
> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
25
25
26
26
> [!NOTE]
27
-
> Azure Kubernetes Service on Azure Stack Hub doesn't support the creation of a cluster in the administration environment. You can only create AKS clusters in the user environment.
27
+
> Azure Kubernetes Service on Azure Stack Hub doesn't support the creation of a cluster in the administrator environment. You can only create AKS clusters in the user environment.
28
28
29
29
## Download required VM extensions
30
30
@@ -36,11 +36,11 @@ You can find the VM extensions in the Azure Stack Hub Marketplace. You can downl
36
36
37
37
- Run command for Linux (latest version)
38
38
39
-
39
+
40
40
41
41
- Custom script for Linux (version 2.0.6)
42
42
43
-
43
+
44
44
45
45
### View the extensions with PowerShell
46
46
@@ -56,50 +56,50 @@ For information about installing and using the AzureStack PowerShell module, see
56
56
57
57
## Download AKS base image
58
58
59
-
The AKS Service needs a special VM image referred to as the *AKS base image*. The AKS service doesn't work without the correct image version available in the local Azure Stack Hub Marketplace. The image is meant to be used by the AKS service, not to be used by tenants to create individual VMs. The image is not visible to tenants in the Marketplace. This is a task that needs to be done along with every Azure Stack Hub update. Every time there is a new update, there is a new AKS base image associated with the AKS service. Here are the steps:
59
+
The AKS service needs a special VM image referred to as the *AKS base image*. The AKS service doesn't work without the correct image version available in the local Azure Stack Hub Marketplace. The image is meant to be used by the AKS service, not to be used by tenants to create individual VMs. The image is not visible to tenants in the Marketplace. This is a task that needs to be done along with every Azure Stack Hub update. Every time there is a new update, there's a new AKS base image associated with the AKS service. Here are the steps:
60
60
61
61
1. Using the administrator portal, go the **Marketplace management** blade and select **Add from Azure**.
62
62
1. Type **AKS** in the search box. Locate and download both the Linux **AKS Base Ubuntu 18.04-LTS Image Distro, 2022 Q1** version **2022.01.21** and the **AKS Base Windows Image** version **17763.2300.220121**.
63
63
64
64
- Linux base image:
65
65
66
-
[](media/aks-add-on/aks-base-image-linux.png#lightbox)
66
+
[](media/aks-add-on/aks-base-image-linux.png#lightbox)
67
67
68
68
- Windows base image:
69
69
70
-
[](media/aks-add-on/aks-base-image-windows.png#lightbox)
70
+
[](media/aks-add-on/aks-base-image-windows.png#lightbox)
71
71
72
-
1. If your instance is disconnected, follow the instructions in the article [Download Marketplace items to Azure Stack Hub](azure-stack-download-azure-marketplace-item.md) to download the two specified items from the marketplace in Azure, and upload them to your Azure Stack Hub instance.
72
+
1. If your instance is disconnected, follow the instructions in [Download Marketplace items to Azure Stack Hub](azure-stack-download-azure-marketplace-item.md) to download the two specified items from the marketplace in Azure, and upload them to your Azure Stack Hub instance.
73
73
74
74
## Create plans and offers
75
75
76
76
To allow tenant users to use the AKS service, the operator must make it available through a plan and an offer.
77
77
78
78
1. Create a plan with the `Microsoft.Container` service. There are no specific quotas for this service; it uses the quotas available for the Compute, Network, and Storage services:
79
79
80
-
80
+
81
81
82
82
1. Again, use the Azure Stack Hub administration portal to create an offer that contains the plan created in the prior step:
83
83
84
-
84
+
85
85
86
86
## Configure multi-tenancy
87
87
88
88
You must configure Azure Stack Hub to support sign-ins from users that reside in other Microsoft Entra directories, allowing them to use services in Azure Stack Hub.
89
89
90
-
For instructions, see [Configure multi-tenancy in Azure Stack Hub](enable-multitenancy.md?pivots=management-tool-powershell)
90
+
For instructions, see [Configure multi-tenancy in Azure Stack Hub](enable-multitenancy.md?pivots=management-tool-powershell).
91
91
92
92
## Monitor and act on alerts
93
93
94
-
1.Using the administrative portal, you can access the**Azure Kubernetes Service** under the **Administration** group.
94
+
1.Use the administrator portal to access **Azure Kubernetes Service** under the **Administration** group.
95
95
1. Select the **Alerts** blade. Review the alerts:
96
96
97
-
97
+
98
98
99
99
1. Alerts appear in the **Alerts** blade, and you can take action on them if necessary:
100
100
101
-
101
+
102
102
103
103
## Next steps
104
104
105
-
[Learn more about AKS on Azure Stack Hub](../user/aks-overview.md)
105
+
[More information about AKS on Azure Stack Hub](../user/aks-overview.md)
Copy file name to clipboardExpand all lines: azure-stack/operator/app-service-back-up.md
+23-21Lines changed: 23 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,10 +2,9 @@
2
2
title: Back up App Service on Azure Stack Hub
3
3
description: Learn how to back up App Services on Azure Stack Hub.
4
4
author: sethmanheim
5
-
6
5
ms.topic: article
7
-
ms.date: 04/23/2019
8
-
ms.author: anwestg
6
+
ms.date: 08/08/2024
7
+
ms.author: sethm
9
8
ms.reviewer: anwestg
10
9
ms.lastreviewed: 03/21/2019
11
10
@@ -16,39 +15,40 @@ ms.lastreviewed: 03/21/2019
16
15
17
16
# Back up App Service on Azure Stack Hub
18
17
19
-
This document provides instructions on how to back up App Service on Azure Stack Hub.
18
+
This article provides instructions on how to back up App Service on Azure Stack Hub.
20
19
21
20
> [!IMPORTANT]
22
-
> App Service on Azure Stack Hub isn't backed up as part of [Azure Stack Hub infrastructure backup](azure-stack-backup-infrastructure-backup.md). As an Azure Stack Hub Operator, you must take steps to ensure App Service can be successfully recovered if necessary.
21
+
> App Service on Azure Stack Hub isn't backed up as part of [Azure Stack Hub infrastructure backup](azure-stack-backup-infrastructure-backup.md). As an Azure Stack Hub operator, you must take steps to ensure App Service can be successfully recovered if necessary.
23
22
24
23
Azure App Service on Azure Stack Hub has four main components to consider when planning for disaster recovery:
25
-
1. The resource provider infrastructure; server roles, worker tiers, and so on.
26
-
2. The App Service secrets.
27
-
3. The App Service SQL Server hosting and metering databases.
28
-
4. The App Service user workload content stored in the App Service file share.
29
24
30
-
## Back up App Service secrets
31
-
When recovering App Service from backup, you need to provide the App Service keys used by the initial deployment. This information should be saved as soon as App Service is successfully deployed and stored in a safe location. The resource provider infrastructure configuration is recreated from backup during recovery using App Service recovery PowerShell cmdlets.
25
+
1. The resource provider infrastructure; server roles, worker tiers, and so on.
26
+
1. The App Service secrets.
27
+
1. The App Service SQL Server hosting and metering databases.
28
+
1. The App Service user workload content stored in the App Service file share.
32
29
33
-
Use the administration portal to back up app service secrets by following these steps:
30
+
## Back up App Service secrets
34
31
35
-
1. Sign in to the Azure Stack Hub administrator portal as the service admin.
32
+
When you recover App Service from backup, you must provide the App Service keys used by the initial deployment. This information should be saved as soon as App Service is successfully deployed and stored in a safe location. The resource provider infrastructure configuration is recreated from backup during recovery using App Service recovery PowerShell cmdlets.
36
33
37
-
2. Browse to **App Service** -> **Secrets**.
34
+
Use the administrator portal to back up App Service secrets by following these steps:
38
35
39
-
3. Select **Download Secrets**.
36
+
1. Sign in to the Azure Stack Hub administrator portal as the service admin.
37
+
1. Browse to **App Service** -> **Secrets**.
38
+
1. Select **Download Secrets**.
40
39
41
-
40
+
42
41
43
-
4. When secrets are ready for downloading, click**Save** and store the App Service secrets (**SystemSecrets.JSON**) file in a safe location.
42
+
1. When the secrets are ready for downloading, select**Save** and store the App Service secrets (**SystemSecrets.json**) file in a safe location.
44
43
45
-
44
+
46
45
47
46
> [!NOTE]
48
47
> Repeat these steps every time the App Service secrets are rotated.
49
48
50
49
## Back up the App Service databases
51
-
To restore App Service, you need the **Appservice_hosting** and **Appservice_metering** database backups. We recommend using SQL Server maintenance plans or Azure Backup Server to ensure these databases are backed up and saved securely on a regular basis. However, any method of ensuring regular SQL backups are created can be used.
50
+
51
+
To restore App Service, you need the **Appservice_hosting** and **Appservice_metering** database backups. We recommend using SQL Server maintenance plans or Azure Backup Server to ensure these databases are backed up and saved securely on a regular basis. However, you can use any method of ensuring regular SQL backups are created.
52
52
53
53
To manually back up these databases while logged into the SQL Server, use the following PowerShell commands:
54
54
@@ -61,16 +61,17 @@ To manually back up these databases while logged into the SQL Server, use the fo
61
61
```
62
62
63
63
> [!NOTE]
64
-
> If you need to back up SQL AlwaysOn databases, follow [these instructions](/sql/database-engine/availability-groups/windows/configure-backup-on-availability-replicas-sql-server?view=sql-server-2017&preserve-view=true).
64
+
> If you need to back up SQL AlwaysOn databases, [follow these instructions](/sql/database-engine/availability-groups/windows/configure-backup-on-availability-replicas-sql-server?view=sql-server-2017&preserve-view=true).
65
65
66
66
After all databases have been successfully backed up, copy the .bak files to a safe location along with the App Service secrets info.
67
67
68
68
## Back up the App Service file share
69
+
69
70
App Service stores tenant app info in the file share. This file share must be backed up on a regular basis along with the App Service databases so that as little data as possible is lost if a restore is required.
70
71
71
72
To back up the App Service file share content, use Azure Backup Server or another method to regularly copy the file share content to the location you've saved all previous recovery info.
72
73
73
-
For example, you can use these steps to use Robocopy from a Windows PowerShell (not PowerShell ISE) console session:
74
+
For example, you can run these commands to use Robocopy from a Windows PowerShell (not PowerShell ISE) console session:
74
75
75
76
```powershell
76
77
$source = "<file share location>"
@@ -81,4 +82,5 @@ net use $destination /delete
81
82
```
82
83
83
84
## Next steps
85
+
84
86
[Restore App Service on Azure Stack Hub](app-service-recover.md)
Copy file name to clipboardExpand all lines: azure-stack/operator/app-service-billing-faq.yml
+6-7Lines changed: 6 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -2,11 +2,10 @@
2
2
metadata:
3
3
title: Azure App Service on Azure Stack Hub billing overview and FAQ
4
4
description: Learn about billing for Azure App Service on Azure Stack Hub.
5
-
author: apwestgarth
6
-
manager: stefsch
5
+
author: sethmanheim
7
6
ms.topic: faq
8
-
ms.date: 05/05/2020
9
-
ms.author: anwestg
7
+
ms.date: 08/08/2024
8
+
ms.author: sethm
10
9
ms.reviewer: anwestg
11
10
ms.lastreviewed: 04/13/2020
12
11
@@ -15,11 +14,11 @@ metadata:
15
14
title: Azure App Service on Azure Stack Hub billing overview and FAQ
16
15
summary: |
17
16
18
-
This article shows how cloud operators are billed for offering Azure App Service on Azure Stack Hub and how they can bill their tenants for using the service.
17
+
This article describes how cloud operators are billed for offering Azure App Service on Azure Stack Hub and how they can bill their tenants for using the service.
19
18
20
19
## Billing overview
21
20
22
-
Azure Stack Hub cloud operators choose to deploy Azure App Service on Azure Stack Hub onto their Azure Stack Hub stamp to offer the tenant capabilities of Azure App Service and Azure Functions to their customers. The Azure App Service resource provider consists of multiple types of roles that can be divided between infrastructure and worker tiers.
21
+
Azure Stack Hub cloud operators can choose to deploy Azure App Service on Azure Stack Hub onto their Azure Stack Hub stamp to offer the tenant capabilities of Azure App Service and Azure Functions to their customers. The Azure App Service resource provider consists of multiple types of roles that can be divided between infrastructure and worker tiers.
23
22
24
23
Infrastructure roles aren't billed because they're required for the core operation of the service. Infrastructure roles can be scaled out as required to support the demands of the cloud operator's tenants. The infrastructure roles are as follows:
25
24
@@ -49,7 +48,7 @@ summary: |
49
48
50
49
Cloud operators can view the current number of available workers per worker tier by looking at the worker tiers in the Azure App Service configuration on Azure Stack Hub administration.
51
50
52
-
51
+
53
52
54
53
## See customer usage by using the Azure Stack Hub usage service
0 commit comments