Skip to content

Commit 28260ea

Browse files
sethmanheimsethmanheim
authored
Merge pull request #15788 from parameshbabu/main
AKS EE and AKS Arc doc updates
2 parents 59d2b4f + 2da97b4 commit 28260ea

File tree

4 files changed

+29
-22
lines changed

4 files changed

+29
-22
lines changed

‎AKS-Hybrid/aks-edge-howto-multi-node-deployment.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,9 @@ You can generate the parameters needed to create a scalable cluster using the fo
2727
New-AksEdgeConfig -DeploymentType ScalableCluster -outFile .\aksedge-config.json | Out-Null
2828
```
2929

30-
This creates a configuration file called **aksedge-config.json** which includes the configuration needed to create a scalable cluster with a Linux node. The file is created in your current working directory. See the following examples for more options for creating the configuration file. A detailed description of the configuration parameters [is available here](aks-edge-deployment-config-json.md).
30+
This command creates a configuration file named **aksedge-config.json**, which includes the configuration needed to create a scalable cluster with a Linux node. The file is created in your current working directory. See [Deployment JSON configuration](aks-edge-deployment-config-json.md) for detailed descriptions of the configuration parameters (such as proxy settings).
31+
32+
See the following examples for more options for creating the configuration file.
3133

3234
The key parameters to note for a scalable Kubernetes deployment are:
3335

‎AKS-Hybrid/aks-edge-howto-single-node-deployment.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ New-AksEdgeConfig -DeploymentType SingleMachineCluster -outFile .\aksedge-config
2626

2727
This command creates a configuration file called **aksedge-config.json** that includes the configuration needed to create a single-machine cluster with a Linux node. The file is created in your current working directory. See the following examples for more options for creating the configuration file.
2828

29-
A detailed description of the configuration parameters [is available here](aks-edge-deployment-config-json.md).
29+
See [Deployment JSON configuration](aks-edge-deployment-config-json.md) for a detailed description of the configuration parameters.
3030

3131
The key parameters for single machine deployment are:
3232

@@ -90,6 +90,9 @@ $machine.LinuxNode.MemoryInMB = 4096
9090
New-AksEdgeDeployment -JsonConfigString ($jsonObj | ConvertTo-Json -Depth 4)
9191
```
9292

93+
> [!TIP]
94+
> See [Deployment JSON configuration](aks-edge-deployment-config-json.md) for all available options, including network settings such as proxy settings.
95+
9396
### Create a simple cluster with NodePort service
9497

9598
You can create a simple cluster with no service IPs (`ServiceIPRangeSize` set as 0):

‎AKS-Hybrid/aks-edge-quickstart.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,9 @@ ms.custom: template-how-to
1212

1313
This quickstart describes how to set up an Azure Kubernetes Service (AKS) Edge Essentials single-machine K3S Linux-only cluster.
1414

15+
> [!NOTE]
16+
> The purpose of this quickstart script is to ease the evaluation process. This script requires higher level credentials for a one-time setup of the Azure subscription. This is not intended for production use.
17+
1518
## Prerequisites
1619

1720
- See the [system requirements](aks-edge-system-requirements.md). For this quickstart, ensure that you have a minimum of 4.5 GB RAM free, 4 vCPUs and 20 GB free disk space.
@@ -53,6 +56,9 @@ This script automates the following steps:
5356
- Installs the Azure Connected Machine Agent and connects the host machine to Arc for Servers.
5457
- Connects the deployed cluster to Arc for connected Kubernetes.
5558

59+
> [!TIP]
60+
> You can modify the `$aksedgeConfig` json content in the `AksEdgeQuickStart` script for any additional options. For available options, see [Deployment JSON configuration](aks-edge-deployment-config-json.md).
61+
5662
## Step 2: Deploy AKS Edge Essentials
5763

5864
In an elevated PowerShell prompt, run the `AksEdgeQuickStart.ps1` script. This brings up a K3s cluster:

‎AKS-Hybrid/scale-requirements.md

Lines changed: 16 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -18,35 +18,31 @@ This article describes the maximum and minimum supported scale count for AKS on
1818

1919
## Support count for AKS on HCI
2020

21-
| Scale item | Count |
22-
|--------------------------------------------------------------------------|--------------------------------------------|
23-
| Minimum number of physical nodes in an Azure Stack HCI cluster | 1 |
24-
| Maximum number of physical nodes in an Azure Stack HCI cluster | 16 |
25-
| Minimum count for control plane node | 1 |
26-
| Maximum count for control plane node | 5 <br /> Allowed values: 1, 3, and 5. |
27-
| Minimum number of nodes in default node pool created during cluster create | 1 |
28-
| Minimum number of node pools in an AKS cluster | 1 |
29-
| Maximum number of node pools in an AKS cluster | 16 |
30-
| Minimum number of nodes in a node pool | 1 <br /> Can't create empty node pools.|
31-
| Maximum number of nodes in a node pool | 64 |
32-
| Maximum number of total nodes in an AKS cluster | 200 |
33-
| Maximum number of AKS clusters per Azure Stack HCI cluster | 32 |
21+
| Scale item | Minimum | Maximum |
22+
|--------------|----------|---------|
23+
| Number of physical nodes in an Azure Stack HCI cluster | 1 | 16 |
24+
| Count of control plane nodes (Allowed values are 1, 3, and 5) | 1 | 5 |
25+
| Number of nodes in default node pool created during cluster create | 1 | 200 |
26+
| Number of node pools in an AKS cluster | 1 | 16 |
27+
| Number of nodes in a node pool (empty node pools not supported) | 1 | 64 |
28+
| Total number of nodes in an AKS cluster across nodepools | 1 | 200 |
29+
| Number of AKS clusters per Azure Stack HCI cluster | 0| 32 |
3430

3531
## Concurrency for AKS enabled by Arc
3632

37-
| Scale item  | Count  |
38-
|-----------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------|
39-
| Number of concurrent AKS cluster creations on an ARB  | 8  |
40-
| Number of concurrent node pool creations on an ARB  | 8  |
41-
| Number of concurrent operations across all different AKS clusters such as upgrade/scaling, etc., excluding creating node pool or clusters per ARB  | 32  |
42-
| Number of long running operations that can be run simultaneously on an AKS cluster  | 1 per cluster.  |
33+
| Scale item  | Count  |
34+
|-------------|--------|
35+
| Number of concurrent AKS cluster creations on an ARB  | 8 |
36+
| Number of concurrent node pool creations on an ARB  | 8  |
37+
| Number of concurrent operations across all different AKS clusters such as upgrade/scaling, etc., excluding creating node pool or clusters per ARB  | 32  |
38+
| Number of long running operations that can be run simultaneously on an AKS cluster  | 1 per cluster.  |
4339

4440
## Default values for virtual machine sizes
4541

4642
| System Role | VM Size | Memory, CPU |
4743
|---------------------------------|----------------------------------------|----------------------|
4844
| AKS Arc control plane nodes | Standard_A4_v2 | 8-GB memory, 4 vcpu |
49-
| AKS Arc HA Proxy VM | Standard_A4_v2. Can't be changed. | 8-GB memory, 4 vcpu |
45+
| AKS Arc HA Proxy VM | Standard_A4_v2. (This size is fixed and can't be changed) | 8-GB memory, 4 vcpu |
5046
| AKS Arc Linux worker node | Standard_K8S3_v1 | 6-GB memory, 4 vcpu |
5147
| AKS Arc Windows worker node | Standard_K8S3_v1 | 6-GB memory, 4 vcpu |
5248

0 commit comments

Comments
 (0)