Skip to content

Commit a2ac0de

Browse files
authored
Merge pull request #104197 from openshift-cherrypick-robot/cherry-pick-104190-to-enterprise-4.21
[enterprise-4.21] Added a section for day2 operator for azure disk encryption sets.
2 parents 7ad25f8 + 49bfb02 commit a2ac0de

File tree

2 files changed

+83
-1
lines changed

2 files changed

+83
-1
lines changed

installing/installing_azure/ipi/installing-azure-preparing-ipi.adoc

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,6 +36,8 @@ include::modules/cluster-telemetry.adoc[leveloffset=+1]
3636

3737
* For more information about the Telemetry service, see xref:../../../support/remote_health_monitoring/about-remote-health-monitoring.adoc#about-remote-health-monitoring[About remote health monitoring]
3838
39+
include::modules/installation-azure-day2-operations-diskencryptionsets.adoc[leveloffset=+1]
40+
3941
include::modules/installation-azure-preparing-diskencryptionsets.adoc[leveloffset=+1]
4042

4143
.Next steps
@@ -44,4 +46,4 @@ include::modules/installation-azure-preparing-diskencryptionsets.adoc[leveloffse
4446
** xref:../../../installing/installing_azure/ipi/installing-azure-customizations.adoc#installing-azure-customizations[Install a cluster with customizations on installer-provisioned infrastructure]
4547
** xref:../../../installing/installing_azure/ipi/installing-azure-vnet.adoc#installing-azure-vnet[Install a cluster into an existing VNet on installer-provisioned infrastructure]
4648
** xref:../../../installing/installing_azure/ipi/installing-azure-private.adoc#installing-azure-private[Install a private cluster on installer-provisioned infrastructure]
47-
** xref:../../../installing/installing_azure/ipi/installing-azure-government-region.adoc#installing-azure-government-region[Install a cluster into an government region on installer-provisioned infrastructure]
49+
** xref:../../../installing/installing_azure/ipi/installing-azure-government-region.adoc#installing-azure-government-region[Install a cluster into an government region on installer-provisioned infrastructure]
Lines changed: 80 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,80 @@
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+
.Procedure
15+
16+
. Mark the node from the `encyptionAtHost` cluster resource group as unschedulable by using the following command:
17+
+
18+
[source,terminal]
19+
----
20+
$ oc adm cordon <node_name>
21+
----
22+
23+
. 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:
24+
+
25+
[source,terminal]
26+
----
27+
$ oc adm drain <compute_node> [--pod-selector=<pod_selector>]
28+
----
29+
+
30+
[NOTE]
31+
====
32+
For other options to evacuate pods from a node, see the "Understanding how to evacuate pods on nodes" section.
33+
====
34+
35+
. De-allocate the node by running the following command:
36+
+
37+
[source,terminal]
38+
----
39+
$ az vm deallocate -n <node_name> -g <cluster_resource_group>
40+
----
41+
42+
. Set the `encryptionAtHost` property to `true` by running the following command:
43+
+
44+
[source,terminal]
45+
----
46+
$ az vm update -n <node_name> -g <cluster_resource_group> --set securityProfile.encryptionAtHost=true
47+
----
48+
49+
. Start the node by running the following commands:
50+
+
51+
[source,terminal]
52+
----
53+
$ az vm start -n <node_name> -g <cluster_resource_group>
54+
----
55+
56+
. Mark the node as schedulable by using the following command:
57+
+
58+
[source,terminal]
59+
----
60+
$ oc adm uncordon <node_name>
61+
----
62+
63+
. Verify that all cluster Operators are available:
64+
+
65+
[source,terminal]
66+
----
67+
$ oc get clusteroperators
68+
----
69+
+
70+
All Operators should show `AVAILABLE=True`, `PROGRESSING=False`, and `DEGRADED=False`.
71+
72+
. Repeat the above steps on all the nodes that run `encryptionAtHost`.
73+
74+
[NOTE]
75+
====
76+
If you want to enable encryption for your host during cluster installation, specify the following parameters in the `install-config.yaml` file:
77+
* `compute.platform.azure.encryptionAtHost`
78+
* `controlPlane.platform.azure.encryptionAtHost`
79+
* `platform.azure.defaultMachinePlatform.encryptionAtHost`
80+
====

0 commit comments

Comments
 (0)