Skip to content

Commit cf157d3

Browse files
author
Justin
committed
fix grammar and implications of uptime sla doc
1 parent de97766 commit cf157d3

File tree

1 file changed

+9
-11
lines changed

1 file changed

+9
-11
lines changed

articles/aks/uptime-sla.md

Lines changed: 9 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,25 +1,25 @@
11
---
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.
2+
title: Azure Kubernetes Service (AKS) with Uptime SLA
3+
description: Learn about the optional Uptime SLA offering for the Azure Kubernetes Service (AKS) API Server.
44
services: container-service
55
ms.topic: conceptual
66
ms.date: 05/11/2020
77
---
88

99
# Azure Kubernetes Service (AKS) Uptime SLA
1010

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.
11+
Uptime SLA is an optional feature to enable a financially backed, higher SLA for a cluster. Uptime SLA guarantees 99.95% availability of the Kubernetes API server endpoint for clusters that use [Availability Zones][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.
1212

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.
13+
Customers needing an SLA to meet compliance requirements or require extending an SLA to their end-users should enable this feature. Customers with critical workloads that will benefit from a higher uptime SLA may also benefit. Using the Uptime SLA feature with Availability Zones enables a higher availability for the uptime of the Kubernetes API server.
1414

15-
Customers can create unlimited free clusters with a service level objective (SLO) of 99.5%.
15+
Customers can still create unlimited free clusters with a service level objective (SLO) of 99.5% and opt for the preferred SLO or SLA Uptime as needed.
1616

1717
> [!Important]
1818
> For clusters with egress lockdown, see [limit egress traffic](limit-egress-traffic.md) to open appropriate ports for Uptime SLA.
1919
2020
## SLA terms and conditions
2121

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.
22+
Uptime SLA is a paid feature and enabled per cluster. Uptime SLA pricing is determined by the number of discrete clusters, and not by the size of the individual clusters. You can view [Uptime SLA pricing details](https://azure.microsoft.com/pricing/details/kubernetes-service/) for more information.
2323

2424
## Region Availability
2525

@@ -59,19 +59,17 @@ After a few minutes, the command completes and returns JSON-formatted informatio
5959
"name": "Basic",
6060
"tier": "Paid"
6161
},
62-
"tags": null,
63-
"type": "Microsoft.ContainerService/ManagedClusters",
64-
"windowsProfile": null
6562
```
6663

6764
## Limitations
6865

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.
66+
* Currently, cannot convert as existing cluster to enable the Uptime SLA.
67+
* Currently, there is no way to remove Uptime SLA from an AKS cluster after creation with it enabled.
7168

7269
## Next steps
7370

7471
Use [Availability Zones][availability-zones] to increase high availability with your AKS cluster workloads.
72+
Configure your cluster to [limit egress traffic](limit-egress-traffic.md).
7573

7674
<!-- LINKS - External -->
7775
[azure-support]: https://ms.portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest

0 commit comments

Comments
 (0)