You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/aks/use-kms-etcd-encryption.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -62,9 +62,9 @@ az provider register --namespace Microsoft.ContainerService
62
62
The following limitations apply when you integrate KMS etcd encryption with AKS:
63
63
64
64
* Disabling of the KMS etcd encryption feature.
65
-
* Changing of key Id, including key name and key version.
65
+
* Changing of key ID, including key name and key version.
66
66
* Deletion of the key, Key Vault, or the associated identity.
67
-
* KMS etcd encryption does not work with System-Assigned Managed Identity. The keyvault access-policy is required to be set before the feature is enabled. In addition, System-Assigned Managed Identity is not available until cluster creation, thus there is a cycle dependency.
67
+
* KMS etcd encryption doesn't work with System-Assigned Managed Identity. The keyvault 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.
68
68
* Using Azure Key Vault with PrivateLink enabled.
69
69
* Using more than 2000 secrets in a cluster.
70
70
* Managed HSM Support
@@ -107,23 +107,23 @@ Use `az identity create` to create a User-assigned managed identity.
107
107
az identity create --name MyIdentity --resource-group MyResourceGroup
0 commit comments