Skip to content

Commit 0ca0eff

Browse files
committed
fix
1 parent 2f8c414 commit 0ca0eff

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

AKS-Hybrid/concepts-support.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ The hardware configuration of each physical node in the Azure Local cluster is a
4646
- Disk: 8x HDDs (2 TB or larger) and 2x 1.6 TB NVMe to support S2D storage configurations.
4747
- Network: Four (4) 100-Gbit NICs (Mellanox or Intel).
4848

49-
Microsoft engineering tested AKS enabled by Arc using the above configuration. For single node. 2 node, 4 node and 8 node Windows failover clusters. If you have a requirement to exceed the tested configuration, see [Scaling AKS on Azure Local](#scaling-aks-on-azure-stack-hci).
49+
Microsoft engineering tested AKS enabled by Arc using the above configuration. For single node. 2 node, 4 node and 8 node Windows failover clusters. If you have a requirement to exceed the tested configuration, see [Scaling AKS on Azure Local](#scaling-aks-on-azure-local).
5050

5151
> [!IMPORTANT]
5252
> When you upgrade a deployment of AKS, extra resources are temporarily consumed.

AKS-Hybrid/deploy-cluster-on-two-node-hci.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.date: 11/01/2024
99

1010
# Availability scenarios for Azure Kubernetes Service (AKS) enabled by Azure Arc on two-node Azure Local
1111

12-
[!INCLUDE [applies-to](../azure-stack/hci/includes/hci-applies-to-22h2.md)]
12+
[!INCLUDE [applies-to](../azure-stack/includes/hci-applies-to-22h2.md)]
1313

1414
This article describes the architecture for deploying a Kubernetes cluster on a two-node Azure Local cluster. The article describes various failure scenarios that can occur, their impact on the cluster, and recoverability from these failure scenarios.
1515

0 commit comments

Comments
 (0)