Skip to content

Commit 2cab738

Browse files
Merge pull request #17208 from sethmanheim/single
Pull commits for single node deployment
2 parents 91116df + a71c112 commit 2cab738

File tree

3 files changed

+8
-5
lines changed

3 files changed

+8
-5
lines changed

AKS-Arc/aks-edge-howto-secret-encryption.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to enable the KMS plugin for AKS Edge Essentials clusters
44
author: sethmanheim
55
ms.author: sethm
66
ms.topic: how-to
7-
ms.date: 02/20/2025
7+
ms.date: 02/27/2025
88
ms.custom: template-how-to
99
ms.reviewer: leslielin
1010
---

AKS-Arc/aks-edge-howto-single-node-deployment.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to deploy AKS Edge Essentials on a single machine.
44
author: sethmanheim
55
ms.author: sethm
66
ms.topic: how-to
7-
ms.date: 02/20/2024
7+
ms.date: 02/27/2025
88
ms.custom: template-how-to
99
---
1010

@@ -35,13 +35,14 @@ The key parameters for single machine deployment are:
3535

3636
- The `Network.NetworkPlugin` by default is `flannel`. This is the default for a K3S cluster. If you're using a K8S cluster, change the CNI to `calico`.
3737
- You can set the following parameters according to your deployment configuration [as described here](aks-edge-deployment-config-json.md): `LinuxNode.CpuCount`, `LinuxNode.MemoryInMB`, `LinuxNode.DataSizeInGB`, `WindowsNode.CpuCount`, `WindowsNode.MemoryInMB`, `Init.ServiceIPRangeSize`, and `Network.InternetDisabled`.
38+
- To encrypt the Kubernetes secret store, you can enable the Key Management Service (KMS) plugin (preview) by setting the `Init.KmsPlugin enable` to **true**. For more information, see [Enable secret encryption on a cluster](aks-edge-howto-secret-encryption.md).
3839

3940
> [!IMPORTANT]
4041
> Starting with the AKS Edge Essentials February 2025 release, the `Arc` section of the config file is required. The Azure Arc connection occurs automatically during the AKS Edge Essentials deployment.
4142
4243
## Step 2: create a single machine cluster
4344

44-
1. You can now run the `New-AksEdgeDeployment` cmdlet to deploy a single-machine AKS Edge cluster with a single Linux control-plane node:
45+
You can now run the `New-AksEdgeDeployment` cmdlet to deploy a single-machine AKS Edge cluster with a single Linux control-plane node:
4546

4647
```powershell
4748
New-AksEdgeDeployment -JsonConfigFilePath .\aksedge-config.json

AKS-Arc/aks-edge-quickstart.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to bring up an AKS Edge Essentials cluster and connect it
44
author: sethmanheim
55
ms.author: sethm
66
ms.topic: quickstart
7-
ms.date: 07/11/2024
7+
ms.date: 02/27/2025
88
ms.custom: template-how-to
99
---
1010

@@ -13,7 +13,9 @@ ms.custom: template-how-to
1313
This quickstart describes how to set up an Azure Kubernetes Service (AKS) Edge Essentials single-machine K3S Linux-only cluster.
1414

1515
> [!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.
16+
>
17+
> - 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. The script is not intended for production use.
18+
> - By default, this quickstart script enables the Key Management Service (KMS) plugin (preview) by setting Init.KmsPlugin to **true**. For more information, see [Enable secret encryption on an AKS Edge Essentials cluster](aks-edge-howto-secret-encryption.md).
1719
1820
## Prerequisites
1921

0 commit comments

Comments
 (0)