|
| 1 | +//Module included in the following assemblies: |
| 2 | +// |
| 3 | +// * installing/installing_azure/enabling-disk-encryption-sets-azure.adoc |
| 4 | + |
| 5 | +:_mod-docs-content-type: PROCEDURE |
| 6 | +[id="installation-azure-day2-operations-diskencryptionsets.adoc_{context}"] |
| 7 | += Preparing an Azure Disk Encryption Set for Day2 Operator |
| 8 | + |
| 9 | +The {product-title} installation program can use an existing Disk Encryption Set with a user-managed key. To enable this feature, create a `DiskEncryptionSet` object in Azure and provide the key to the installation program. |
| 10 | + |
| 11 | +.Prerequisite |
| 12 | + |
| 13 | +* You enabled the `EncryptionAtHost` feature in your {azure-short} subscription. For more information, see "Use the Azure portal to enable end-to-end encryption using encryption at host". |
| 14 | +
|
| 15 | +.Procedure |
| 16 | + |
| 17 | +. Mark the node from the `encyptionAtHost` cluster resource group as unschedulable by using the following command: |
| 18 | ++ |
| 19 | +[source,terminal] |
| 20 | +---- |
| 21 | +$ oc adm cordon <node_name> |
| 22 | +---- |
| 23 | + |
| 24 | +. Evacuate the pods from the compute node. There are several ways to do this. For example, you can evacuate all the pods or the selected pods on a node: |
| 25 | ++ |
| 26 | +[source,terminal] |
| 27 | +---- |
| 28 | +$ oc adm drain <compute_node> [--pod-selector=<pod_selector>] |
| 29 | +---- |
| 30 | ++ |
| 31 | +[NOTE] |
| 32 | +==== |
| 33 | +For other options to evacuate pods from a node, see the "Understanding how to evacuate pods on nodes" section. |
| 34 | +==== |
| 35 | + |
| 36 | +. De-allocate the node by running the following command: |
| 37 | ++ |
| 38 | +[source,terminal] |
| 39 | +---- |
| 40 | +$ az vm deallocate -n <node_name> -g <cluster_resource_group> |
| 41 | +---- |
| 42 | + |
| 43 | +. Set the `encryptionAtHost` property to `true` by running the following command: |
| 44 | ++ |
| 45 | +[source,terminal] |
| 46 | +---- |
| 47 | +$ az vm update -n <node_name> -g <cluster_resource_group> --set securityProfile.encryptionAtHost=true |
| 48 | +---- |
| 49 | + |
| 50 | +. Start the node by running the following commands: |
| 51 | ++ |
| 52 | +[source,terminal] |
| 53 | +---- |
| 54 | +$ az vm start -n <node_name> -g <cluster_resource_group> |
| 55 | +---- |
| 56 | + |
| 57 | +. Mark the node as schedulable by using the following command: |
| 58 | ++ |
| 59 | +[source,terminal] |
| 60 | +---- |
| 61 | +$ oc adm uncordon <node_name> |
| 62 | +---- |
| 63 | + |
| 64 | +. Verify that all cluster Operators are available: |
| 65 | ++ |
| 66 | +[source,terminal] |
| 67 | +---- |
| 68 | +$ oc get clusteroperators |
| 69 | +---- |
| 70 | ++ |
| 71 | +All Operators should show `AVAILABLE=True`, `PROGRESSING=False`, and `DEGRADED=False`. |
| 72 | + |
| 73 | +. Repeat the above steps on all the nodes that run `encryptionAtHost`. |
| 74 | + |
| 75 | +[NOTE] |
| 76 | +==== |
| 77 | +If you want to enable encryption for your host during cluster installation, specify the following parameters in the `install-config.yaml` file: |
| 78 | +
|
| 79 | +* `compute.platform.azure.encryptionAtHost` |
| 80 | +* `controlPlane.platform.azure.encryptionAtHost` |
| 81 | +* `platform.azure.defaultMachinePlatform.encryptionAtHost` |
| 82 | +==== |
0 commit comments