Skip to content

Commit 03abede

Browse files
Merge pull request #286284 from johnmarco/jm-aro-cmk-update
ARO: CMK update
2 parents 15fba42 + 339a728 commit 03abede

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

articles/openshift/howto-byok.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: johnmarc
66
ms.service: azure-redhat-openshift
77
keywords: encryption, byok, deploy, openshift, red hat, key
88
ms.topic: how-to
9-
ms.date: 05/05/2023
9+
ms.date: 09/06/2024
1010
ms.custom: template-how-to, devx-track-azurecli
1111
ms.devlang: azurecli
1212
---
@@ -104,6 +104,11 @@ az keyvault set-policy -n $KEYVAULT_NAME \
104104

105105
## Create an Azure Red Hat OpenShift cluster
106106
Create an Azure Red Hat OpenShift cluster to use the customer-managed keys.
107+
108+
> [!NOTE]
109+
> Enabling CMK on *existing* ARO clusters is only possible for worker nodes, not master nodes. You can achieve this using machine-API through machineset CRs. See [Enabling customer-managed encryption keys for a machine set](https://docs.openshift.com/container-platform/4.12/machine_management/creating_machinesets/creating-machineset-azure.html#machineset-enabling-customer-managed-encryption-azure_creating-machineset-azure) and [Modifying a compute machine set](https://docs.openshift.com/container-platform/4.12/machine_management/modifying-machineset.html) for more information.
110+
>
111+
107112
```azurecli-interactive
108113
az aro create --resource-group $RESOURCEGROUP \
109114
--name $CLUSTER \

0 commit comments

Comments
 (0)