Skip to content

Commit c60e430

Browse files
Merge pull request #221817 from CocoWang-wql/patch-20
Update use-kms-etcd-encryption.md
2 parents 7db923a + 5dcbba9 commit c60e430

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/aks/use-kms-etcd-encryption.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Use Key Management Service (KMS) etcd encryption in Azure Kubernetes Serv
33
description: Learn how to use the Key Management Service (KMS) etcd encryption with Azure Kubernetes Service (AKS)
44
services: container-service
55
ms.topic: article
6-
ms.date: 11/09/2022
6+
ms.date: 12/17/2022
77
---
88

99
# Add Key Management Service (KMS) etcd encryption to an Azure Kubernetes Service (AKS) cluster
@@ -30,11 +30,11 @@ For more information on using the KMS plugin, see [Encrypting Secret Data at Res
3030

3131
The following limitations apply when you integrate KMS etcd encryption with AKS:
3232

33-
* Deletion of the key, Key Vault, or the associated identity.
33+
* Deletion of the key, Key Vault, or the associated identity isn't supported.
3434
* KMS etcd encryption doesn't work with system-assigned managed identity. The key vault access policy is required to be set before the feature is enabled. In addition, system-assigned managed identity isn't available until cluster creation, thus there's a cycle dependency.
35-
* Using more than 2000 secrets in a cluster.
36-
* Bring your own (BYO) Azure Key Vault from another tenant.
37-
* Change associated Azure Key Vault model (public, private) if KMS is enabled. For [changing associated key vault mode][changing-associated-key-vault-mode], you need to disable and enable KMS again.
35+
* The maximum number of secrets that a cluster enabled with KMS supports is 2,000.
36+
* Bring your own (BYO) Azure Key Vault from another tenant isn't supported.
37+
* With KMS enabled, you can't change associated Azure Key Vault model (public, private). To [change associated key vault mode][changing-associated-key-vault-mode], you need to disable and enable KMS again.
3838
* If a cluster is enabled KMS with private key vault and not using `VNet integration` tunnel, then stop/start cluster is not allowed.
3939

4040
KMS supports [public key vault][Enable-KMS-with-public-key-vault] and [private key vault][Enable-KMS-with-private-key-vault].

0 commit comments

Comments
 (0)