Skip to content

Commit d3bc14b

Browse files
authored
Update use-kms-etcd-encryption.md
1 parent ca05914 commit d3bc14b

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

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

Lines changed: 3 additions & 1 deletion
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: 01/09/2023
6+
ms.date: 01/17/2023
77
---
88

99
# Add Key Management Service (KMS) etcd encryption to an Azure Kubernetes Service (AKS) cluster
@@ -173,6 +173,8 @@ After changing the key ID (including key name and key version), you can use [az
173173

174174
> [!WARNING]
175175
> Remember to update all secrets after key rotation. Otherwise, the secrets will be inaccessible if the old keys don't exist or aren't working.
176+
>
177+
> Once you rotate the key, the old key (key1) is still cached and shouldn't be deleted. If you want to delete the old key (key1) immediately, you need to rotate the key twice. Then key2 and key3 are cached, and key1 can be deleted without impacting existing cluster.
176178
177179
```azurecli-interactive
178180
az aks update --name myAKSCluster --resource-group MyResourceGroup --enable-azure-keyvault-kms --azure-keyvault-kms-key-vault-network-access "Public" --azure-keyvault-kms-key-id $NEW_KEY_ID

0 commit comments

Comments
 (0)