Skip to content

Commit 996eb47

Browse files
authored
Sync release-local-24113 with main
Sync release-local-24113 with main
2 parents 5c6b59b + f8d306b commit 996eb47

File tree

3 files changed

+4
-5
lines changed

3 files changed

+4
-5
lines changed

azure-local/concepts/system-requirements-23h2.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: alkohli
66
ms.topic: how-to
77
ms.service: azure-local
88
ms.custom: references_regions
9-
ms.date: 02/14/2025
9+
ms.date: 02/21/2025
1010
---
1111

1212
# System requirements for Azure Local
@@ -47,8 +47,8 @@ Before you begin, make sure that the physical machine and storage hardware used
4747

4848
|Component|Minimum|
4949
|--|--|
50-
|Number of machines| 1 to 16 machines are supported. <br> Each machine must be the same model, manufacturer, have the same network adapters, and have the same number and type of storage drives.|
51-
|CPU|A 64-bit Intel Nehalem grade or AMD EPYC or later compatible processor with second-level address translation (SLAT).|
50+
|Number of machines| 1 to 16 machines are supported. <br> Each machine must be the same model, manufacturer, have the same processor types, have the same network adapters, and have the same number and type of storage drives.|
51+
|CPU|A 64-bit Intel Nehalem grade or AMD EPYC or later compatible processor with second-level address translation (SLAT). <br> All the Azure Local machines used to form an Azure Local instance must have the same processor types. |
5252
|Memory|A minimum of 32-GB RAM per machine with Error-Correcting Code (ECC). <br> If you can't meet the memory and the ECC requirements, opt for a [Virtual deployment](../deploy/deployment-virtual.md).|
5353
|Host network adapters|At least two network adapters listed in the Windows Server Catalog. Or dedicated network adapters per intent, which does require two separate adapters for storage intent. For more information, see [Windows Server Catalog](https://www.windowsservercatalog.com/).|
5454
|BIOS|Intel VT or AMD-V must be turned on.|

azure-stack/user/aks-how-to-store-secrets.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Use Azure Key Vault to store secrets with Azure Kubernetes Service on Azu
33
description: Learn how to use Azure Key Vault to store secrets with Azure Kubernetes Service on Azure Stack Hub
44
author: sethmanheim
55
ms.topic: article
6-
ms.date: 11/21/2022
6+
ms.date: 02/14/2025
77
ms.author: sethm
88
ms.reviewer: waltero
99
ms.lastreviewed: 10/26/2021
@@ -33,7 +33,6 @@ You can use the Secrets Store CSI driver to mount your secrets, keys, and certif
3333
3. Learn [how to use the Azure Key Vault Provider](https://azure.github.io/secrets-store-csi-driver-provider-azure/docs/getting-started/usage/) and supported [configurations](https://azure.github.io/secrets-store-csi-driver-provider-azure/docs/configurations/).
3434
4. Get up to speed with the application workflow with the [walkthrough](https://azure.github.io/secrets-store-csi-driver-provider-azure/docs/demos/standard-walkthrough/).
3535

36-
![Secrets Store CSI Driver Azure Key Vault Provider Demo](media/aks-how-to-store-secrets/demo.gif)
3736
## Support for the driver
3837

3938
Azure Key Vault Provider for Secrets Store CSI Driver is an open source project that is [**not** covered by the Microsoft Azure support policy](https://support.microsoft.com/help/2941892/support-for-linux-and-open-source-technology-in-azure). [Please search open issues here](https://github.com/Azure/secrets-store-csi-driver-provider-azure/issues), and if your issue isn't already represented [open a new one](https://github.com/Azure/secrets-store-csi-driver-provider-azure/issues/new/choose). The project maintainers will respond to the best of their abilities.
Binary file not shown.

0 commit comments

Comments
 (0)