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/user/aks-overview.md
+24-24Lines changed: 24 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,24 +3,24 @@ title: Azure Kubernetes Service on Azure Stack Hub overview for users
3
3
description: Learn about Azure Kubernetes Service (ASK) on Azure Stack Hub overview for users.
4
4
author: sethmanheim
5
5
ms.topic: article
6
-
ms.date: 01/24/2025
6
+
ms.date: 02/27/2025
7
7
ms.author: sethm
8
-
ms.lastreviewed: 10/26/2021
8
+
ms.reviewer: sumsmith
9
+
ms.lastreviewed: 02/27/2025
9
10
10
11
# Intent: As an Azure Stack operator, I want to install and offer Azure Kubernetes Service on Azure Stack Hub so my supported user can offer containerized solutions.
11
12
# Keyword: Kubernetes AKS difference
12
13
---
13
14
14
15
# Azure Kubernetes Service on Azure Stack Hub overview for users
15
16
17
+
> [!IMPORTANT]
18
+
> Azure Kubernetes Service on Azure Stack Hub, previously a preview feature, was discontinued and is no longer supported. See the [AKS engine](../user/azure-stack-kubernetes-aks-engine-overview.md) documentation for a Kubernetes solution on Azure Stack Hub.
19
+
16
20
Azure Kubernetes Service (AKS) makes it easy to deploy a Kubernetes cluster in Azure and Azure Stack Hub. AKS reduces the complexity and operational overhead of managing Kubernetes clusters.
17
21
18
22
As a managed Kubernetes service, Azure Stack Hub handles critical tasks such as health monitoring, and facilitates maintenance for you. The Azure Stack Hub team manages the image used for maintaining the clusters. The cluster administrator only needs to apply the updates as needed. The services come at no extra cost. AKS is free; you only pay to use the VMs (master and agent nodes) within your clusters. It's simpler to use than the [AKS engine](azure-stack-kubernetes-aks-engine-overview.md) since it removes some of the manual tasks required with the AKS engine.
19
23
20
-
> [!IMPORTANT]
21
-
> 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.
22
-
> 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.
23
-
24
24
## AKS on Azure Stack Hub
25
25
26
26
You can manage AKS clusters on Azure Stack Hub in the same way you do on the Azure cloud using the same Azure CLI, Azure Stack Hub user portal, Azure Resource Manager templates, and REST API. When you deploy an AKS cluster, the Kubernetes master and all nodes are deployed and configured for you.
@@ -33,17 +33,17 @@ For more information on Kubernetes concepts, check out the [Kubernetes documenta
33
33
34
34
The following tasks fall on the Azure Stack Hub operator:
35
35
36
-
1. Make sure that the Azure Kubernetes Service base images are available in the Azure Stack Hub instance, this includes downloading them from Azure.
37
-
2. Make sure that the Azure Kubernetes Service is available for customers plans and user subscriptions, as is the case with any other service in Azure Stack Hub.
38
-
3. Monitor the Azure Kubernetes Service and act on any alert and associated remediation.
39
-
4. For details on the Operator tasks see [Install and offer the Azure Kubernetes Service on Azure Stack Hub](../operator/aks-add-on.md)
36
+
1. Make sure that the Azure Kubernetes Service base images are available in the Azure Stack Hub instance. If necessary, download them from Azure.
37
+
1. Make sure that the Azure Kubernetes Service is available for customers plans and user subscriptions, as is the case with any other service in Azure Stack Hub.
38
+
1. Monitor the Azure Kubernetes Service and act on any alert and associated remediation.
39
+
1. For details on the Operator tasks see [Install and offer the Azure Kubernetes Service on Azure Stack Hub](../operator/aks-add-on.md)
40
40
41
41
The following tasks correspond to the user; that is, the tenant AKS cluster administrator:
42
42
43
-
1. Monitor the Kubernetes cluster agents' health and act on any event and associated remediation. Even though the masters are created within the tenant subscription, the service will monitor their state and will perform remediation steps as needed. However, there may be support scenarios in which the Tenant Cluster Administrator may be needed to bring back the cluster to a healthy state.
44
-
2. Use the Azure Kubernetes Service facilities to manage the lifecycle of the cluster, that is creation, upgrade, and scale operations.
45
-
3. Maintenance operations: deploy applications, backup and restore, troubleshooting, collection of logs, and monitoring apps.
46
-
4. For Details on the tenant tasks see [ Using Azure Kubernetes Service on Azure Stack Hub with the CLI](aks-how-to-use-cli.md)
43
+
1. Monitor the Kubernetes cluster agents' health and act on any event and associated remediation. Even though the agents are created within the tenant subscription, the service monitors their state and performs remediation steps as needed. However, there might be support scenarios in which the Tenant Cluster Administrator is needed to bring back the cluster to a healthy state.
44
+
1. Use the Azure Kubernetes Service facilities to manage the lifecycle of the cluster, for creation, upgrade, and scale operations.
45
+
1. Maintenance operations: deploy applications, backup and restore, troubleshooting, collection of logs, and monitoring apps.
46
+
1. For Details on the tenant tasks see [ Using Azure Kubernetes Service on Azure Stack Hub with the CLI](aks-how-to-use-cli.md)
47
47
48
48
## Feature comparison
49
49
@@ -70,7 +70,7 @@ The following table provides an overview of features of AKS in global Azure comp
70
70
|| Automatic pod scaling | Yes | Yes |
71
71
|| GPU enable pods | Yes | No |
72
72
|| Storage volume support | Yes | Yes |
73
-
|| Multiple nodepool management | Yes | No |
73
+
|| Multiple node pool management | Yes | No |
74
74
|| Azure Container Instance integration and virtual nodes | Yes | No |
75
75
|| Uptime SLA | Yes | No |
76
76
|| Hidden master nodes | Yes | No |
@@ -94,9 +94,9 @@ The following table provides an overview of features of AKS in global Azure comp
94
94
95
95
## Differences between Azure and Azure Stack Hub
96
96
97
-
AKS on Azure and on Azure Stack Hubs share the same source repository. There are no conceptual differences between the two. However, operating in different environments brings along differences to keep in mind when using AKS on Azure Stack Hub. Most of the differences are related to the system residing inside customers' Data Centers and related to functionality that is not yet available in Azure Stack Hub.
97
+
AKS on Azure and on Azure Stack Hubs share the same source repository. There are no conceptual differences between the two. However, operating in different environments brings along differences to keep in mind when using AKS on Azure Stack Hub. Most of the differences are related to the system residing inside customers' Data Centers and related to functionality that isn't yet available in Azure Stack Hub.
98
98
99
-
### Connected or Disconnected Azure Stack Hub in customer's data center
99
+
### Connected or Disconnected Azure Stack Hub in customer's data center
100
100
101
101
In both scenarios, Azure Stack Hub is under the control of the customer. Also, customers may deploy Azure Stack Hub in fully disconnected, an *air-gapped*, environment. You might want to consider the following factors:
102
102
@@ -118,14 +118,14 @@ When you use the Azure CLI to connect to Azure, the CLI binary defaults to using
118
118
119
119
Azure Stack Hub supports a subset of the features available in global Azure. Note the following differences:
120
120
121
-
- No Standard Load Balancer. Azure Stack Hub only supports the basic load balancer. This implies that the following features, which depend on Standard Load Balancer, are not yet available with AKS on Azure Stack Hub:
121
+
- No Standard Load Balancer. Azure Stack Hub only supports the basic load balancer. This support implies that the following features, which depend on the standard load balancer, aren't yet available with AKS on Azure Stack Hub:
122
122
- No parameter for [API server authorized IP ranges](/azure/aks/api-server-authorized-ip-ranges).
123
123
- No parameter for [load balancer managed ip count](/azure/aks/load-balancer-standard#scale-the-number-of-managed-outbound-public-ips).
124
124
- No parameter for [enabling private cluster](/azure/aks/private-clusters).
125
125
- No [cluster autoscaler](/azure/aks/cluster-autoscaler).
126
126
-[az aks update](/cli/azure/aks#az-aks-update) isn't available.
127
-
- No multiple nodepool support. The nodepool commands aren't available.
128
-
- UI support for multiple nodepool operations isn't enabled.
127
+
- No multiple node pool support. The node pool commands aren't available.
128
+
- UI support for multiple node pool operations isn't enabled.
129
129
- No Azure regions or Availability Zones.
130
130
- No Availability Sets, only virtual machine scale sets.
131
131
- Review command list for supported and unsupported commands.
@@ -135,16 +135,16 @@ Azure Stack Hub supports a subset of the features available in global Azure. Not
135
135
The absence of some Azure services limits some functionality options in AKS on Azure Stack Hub:
136
136
137
137
- No file service. There's no support for file service-based volumes in Kubernetes on Azure Stack Hub.
138
-
- No Azure Log Analytics and Azure Container Monitor. Any Kubernetes cluster can be connected to Azure Container Monitor as long as it is connected to the internet. If it's disconnected, there's no equivalent service locally in Azure Stack Hub. Therefore, there's no integrated support for Azure Container Monitor in AKS on Azure Stack Hub.
139
-
- No Azure DevOps. Since this service is not available for a disconnected Azure Stack Hub, there's no integrated support for it.
138
+
- No Azure Log Analytics and Azure Container Monitor. Any Kubernetes cluster can be connected to Azure Container Monitor as long as it's connected to the internet. If it's disconnected, there's no equivalent service locally in Azure Stack Hub. Therefore, there's no integrated support for Azure Container Monitor in AKS on Azure Stack Hub.
139
+
- No Azure DevOps. Since this service isn't available for a disconnected Azure Stack Hub, there's no integrated support for it.
140
140
141
141
### Supported AKS API and Kubernetes versions
142
142
143
-
Often, Azure Stack Hub AKS falls behind Azure in the versions supported for Kubernetes and AKS API. This is due to the difficulties of shipping code for customers to run in their own datacenters.
143
+
Often, AKS on Azure Stack Hub falls behind Azure in the versions supported for Kubernetes and AKS API. This lack of support is due to the difficulties of shipping code for customers to run in their own datacenters.
144
144
145
145
### Default Azure AKS CLI parameter values to change when using AKS CLI on Azure Stack Hub
146
146
147
-
Given the differences between the two platforms, you should be aware that some default values in parameters in commands and API that work on Azure AKS, do not on Azure Stack Hub AKS. For example:
147
+
Given the differences between the two platforms, some default values of parameters in commands and API that work on Azure AKS, don't work on Azure Stack Hub AKS. For example:
Copy file name to clipboardExpand all lines: azure-stack/user/migrate-azure-stack-to-aks-engine.md
+6-3Lines changed: 6 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,19 +1,22 @@
1
1
---
2
2
title: Migrate workloads to AKS engine from AKS preview on Azure Stack Hub
3
-
description: Find out how to migrate workloads from the AKS preview on Azure Stack Hub to a Kubernetes cluster created in AKS engine. Compare supported Azure Kubernetes Service features.
3
+
description: Learn how to migrate workloads from the AKS preview on Azure Stack Hub to a Kubernetes cluster created in AKS engine and compare supported Azure Kubernetes Service features.
4
4
author: sethmanheim
5
5
ms.topic: article
6
-
ms.date: 01/18/2023
6
+
ms.date: 02/27/2025
7
7
ms.author: sethm
8
8
ms.reviewer: sumsmith
9
-
ms.lastreviewed: 01/18/2023
9
+
ms.lastreviewed: 02/27/2025
10
10
11
11
# Intent: As an Azure Stack operator, I need to know how to migrate my existing deployments in AKS preview to AKS engine and what to expect after I migrate the applications.
12
12
# Keyword: Kubernetes AKS Engine difference
13
13
---
14
14
15
15
# Migrate workloads to AKS engine from AKS preview on Azure Stack Hub
16
16
17
+
> [!IMPORTANT]
18
+
> Azure Kubernetes Service on Azure Stack Hub, previously a preview feature, was discontinued and is no longer supported. See the [AKS engine](../user/azure-stack-kubernetes-aks-engine-overview.md) documentation for a Kubernetes solution on Azure Stack Hub.
19
+
17
20
This article explains how to migrate existing workloads in the Azure Kubernetes Service (AKS) preview on Azure Stack Hub to AKS engine, and summarizes AKS feature differences. The AKS preview is being deprecated in favor of extending support for AKS engine on Azure Stack Hub.
18
21
19
22
[AKS engine](https://github.com/Azure/aks-engine) provides a command-line tool to bootstrap Kubernetes clusters on Azure and Azure Stack Hub. By using Azure Resource Manager, AKS engine helps you create and maintain clusters running on VMs, virtual networks, and other Azure infrastructure as a service (IaaS) resources in Azure Stack Hub. To learn more about AKS engine, see the [AKS engine overview](azure-stack-kubernetes-aks-engine-overview.md), and review the [AKS engine feature comparison](#compare-features-aks-engine-vs-aks-preview) in this article.
0 commit comments