Skip to content

Commit d25aa3b

Browse files
megvanhuygenmegvanhuygen
authored
Merge pull request #106648 from mlearned/mdl-1668649-paid-sku-sla
paid sku branch swap
2 parents 6f1fdfb + 69b62c3 commit d25aa3b

File tree

3 files changed

+95
-2
lines changed

3 files changed

+95
-2
lines changed

‎articles/aks/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -129,6 +129,8 @@
129129
href: scale-cluster.md
130130
- name: Upgrade an AKS cluster
131131
href: upgrade-cluster.md
132+
- name: Use Uptime SLA
133+
href: uptime-sla.md
132134
- name: Process node OS updates
133135
href: node-updates-kured.md
134136
- name: Configure an AKS cluster

‎articles/aks/faq.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -123,6 +123,8 @@ Windows Server support for node pool includes some limitations that are part of
123123

124124
## Does AKS offer a service-level agreement?
125125

126+
AKS provides the ability to achieve 99.95% availability for the API server with [Uptime SLA][uptime-sla.md].
127+
126128
In a service-level agreement (SLA), the provider agrees to reimburse the customer for the cost of the service if the published service level isn't met. Since AKS is free, no cost is available to reimburse, so AKS has no formal SLA. However, AKS seeks to maintain availability of at least 99.5 percent for the Kubernetes API server.
127129

128130
It is important to recognize the distinction between AKS service availability which refers to uptime of the Kubernetes control plane and the availability of your specific workload which is running on Azure Virtual Machines. Although the control plane may be unavailable if the control plane is not ready, your cluster workloads running on Azure VMs can still function. Given Azure VMs are paid resources they are backed by a financial SLA. Read [here for more details](https://azure.microsoft.com/support/legal/sla/virtual-machines/v1_8/) on the Azure VM SLA and how to increase that availability with features like [Availability Zones][availability-zones].
@@ -139,7 +141,7 @@ The `az aks update-credentials` command can be used to move an AKS cluster betwe
139141

140142
Movement of clusters between subscriptions is currently unsupported.
141143

142-
## Can I move my AKS clusters from the current azure subscription to another?
144+
## Can I move my AKS clusters from the current Azure subscription to another?
143145

144146
Moving your AKS cluster and it's associated resources between Azure subscriptions is not supported.
145147

@@ -205,11 +207,12 @@ No AKS is a managed service, and manipulation of the IaaS resources is not suppo
205207
[bcdr-bestpractices]: ./operator-best-practices-multi-region.md#plan-for-multiregion-deployment
206208
[availability-zones]: ./availability-zones.md
207209
[az-regions]: ../availability-zones/az-region.md
210+
[uptime-sla] ./uptime-sla.md
208211

209212
<!-- LINKS - external -->
210213
[aks-regions]: https://azure.microsoft.com/global-infrastructure/services/?products=kubernetes-service
211214
[auto-scaler]: https://github.com/kubernetes/autoscaler
212215
[cordon-drain]: https://kubernetes.io/docs/tasks/administer-cluster/safely-drain-node/
213216
[admission-controllers]: https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/
214217
[private-clusters-github-issue]: https://github.com/Azure/AKS/issues/948
215-
[csi-driver]: https://github.com/Azure/secrets-store-csi-driver-provider-azure
218+
[csi-driver]: https://github.com/Azure/secrets-store-csi-driver-provider-azure

‎articles/aks/uptime-sla.md

Lines changed: 88 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,88 @@
1+
---
2+
title: Azure Kubernetes Service (AKS) high availability with Uptime SLA
3+
description: Learn about the optional high availability Uptime SLA offering for the Azure Kubernetes Service (AKS) API Server.
4+
services: container-service
5+
ms.topic: conceptual
6+
ms.date: 05/11/2020
7+
---
8+
9+
# Azure Kubernetes Service (AKS) Uptime SLA
10+
11+
Uptime SLA is an optional feature to enable financially backed higher SLA for a cluster. Uptime SLA guarantees 99.95% availability of the Kubernetes API server endpoint for clusters that use [Availability Zone][availability-zones] and 99.9% of availability for clusters that don't use availability zones. AKS uses master node replicas across update and fault domains to ensure SLA requirements are met.
12+
13+
Customers needing SLA for compliance reasons or extending SLA's to their customers should turn on this feature. Customers with critical workloads who need higher availability with an option of SLA benefit from enabling this feature. Enable the feature with Availability Zones to obtain higher availability of the Kubernetes API server.
14+
15+
Customers can create unlimited free clusters with a service level objective (SLO) of 99.5%.
16+
17+
> [!Important]
18+
> For clusters with egress lockdown, see [limit egress traffic](limit-egress-traffic.md) to open appropriate ports for Uptime SLA.
19+
20+
## SLA terms and conditions
21+
22+
Uptime SLA is a paid feature and enabled per cluster. Uptime SLA pricing is determined by the number of clusters, and not by the size of the clusters. You can view [Uptime SLA pricing details](https://azure.microsoft.com/pricing/details/kubernetes-service/) for more information.
23+
24+
## Region Availability
25+
26+
Uptime SLA is available in the following regions:
27+
28+
* Australia East
29+
* Canada Central
30+
* East US
31+
* East US 2
32+
* South Central US
33+
* South East Asia
34+
* West US 2
35+
36+
## Before you begin
37+
38+
* The Azure CLI version 2.7.0 or later
39+
40+
## Creating a cluster with Uptime SLA
41+
42+
To create a new cluster with the Uptime SLA, you use the Azure CLI.
43+
44+
The following example creates a resource group named *myResourceGroup* in the *eastus* location.
45+
46+
```azurecli-interactive
47+
az group create --name myResourceGroup --location eastus
48+
```
49+
Use the [az aks create][az-aks-create] command to create an AKS cluster. The following example creates a cluster named *myAKSCluster* with one node. Azure Monitor for containers is also enabled using the *--enable-addons monitoring* parameter. This operation takes several minutes to complete.
50+
51+
```azurecli-interactive
52+
az aks create --resource-group myResourceGroup --name myAKSCluster --uptime-sla --node-count 1 --enable-addons monitoring --generate-ssh-keys
53+
```
54+
After a few minutes, the command completes and returns JSON-formatted information about the cluster. The following JSON snippet shows the paid tier for the SKU, indicating your cluster is enabled with Uptime SLA.
55+
56+
```output
57+
},
58+
"sku": {
59+
"name": "Basic",
60+
"tier": "Paid"
61+
},
62+
"tags": null,
63+
"type": "Microsoft.ContainerService/ManagedClusters",
64+
"windowsProfile": null
65+
```
66+
67+
## Limitations
68+
69+
* You can't currently add Uptime SLA to existing clusters.
70+
* Currently, there is no way to remove Uptime SLA from an AKS cluster.
71+
72+
## Next steps
73+
74+
Use [Availability Zones][availability-zones] to increase high availability with your AKS cluster workloads.
75+
76+
<!-- LINKS - External -->
77+
[azure-support]: https://ms.portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest
78+
[region-availability]: https://azure.microsoft.com/global-infrastructure/services/?products=kubernetes-service
79+
80+
<!-- LINKS - Internal -->
81+
[vm-skus]: ../virtual-machines/linux/sizes.md
82+
[nodepool-upgrade]: use-multiple-node-pools.md#upgrade-a-node-pool
83+
[faq]: ./faq.md
84+
[availability-zones]: ./availability-zones.md
85+
[az-aks-create]: /cli/azure/aks?view=azure-cli-latest#az-aks-create
86+
[limit-egress-traffic]: ./limit-egress-traffic.md
87+
[az-extension-add]: /cli/azure/extension#az-extension-add
88+
[az-extension-update]: /cli/azure/extension#az-extension-update

0 commit comments

Comments
 (0)