Skip to content

[enterprise-4.22] OSDOCS-17043_2_a: CQA Azure machine set assembly and core modules #115939

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
brendan-daly-red-hat merged 1 commit into from
Jul 22, 2026
Merged

[enterprise-4.22] OSDOCS-17043_2_a: CQA Azure machine set assembly and core modules #115939

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion machine_management/creating_machinesets/creating-machineset-azure.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,7 @@ include::modules/machineset-azure-ultra-disk.adoc[leveloffset=+1]

[role="_additional-resources"]
.Additional resources
* link:https://docs.microsoft.com/en-us/azure/virtual-machines/disks-types#ultra-disks[{azure-full} ultra disks documentation]
* link:https://docs.microsoft.com/en-us/azure/virtual-machines/disks-types#ultra-disks[Ultra disks ({azure-short} documentation)]
* xref:../../storage/container_storage_interface/persistent-storage-csi-azure.adoc#machineset-azure-ultra-disk_persistent-storage-csi-azure[Machine sets that deploy machines on ultra disks using CSI PVCs]
* xref:../../storage/persistent_storage/persistent-storage-azure.adoc#machineset-azure-ultra-disk_persistent-storage-azure[Machine sets that deploy machines on ultra disks using in-tree PVCs]

Expand Down Expand Up @@ -86,6 +86,7 @@ include::modules/nvidia-gpu-aws-deploying-the-node-feature-discovery-operator.ad

[role="_additional-resources"]
.Additional resources

* xref:../../installing/installing_azure/ipi/installing-azure-customizations.adoc#machineset-azure-enabling-accelerated-networking-new-install_installing-azure-customizations[Enabling Accelerated Networking during installation]

// Enabling Accelerated Networking on an existing Microsoft Azure cluster
Expand Down
4 changes: 2 additions & 2 deletions modules/machineset-azure-ephemeral-os.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,9 +7,9 @@
= Machine sets that deploy machines on Ephemeral OS disks

[role="_abstract"]
You can create a compute machine set running on {azure-first} that deploys machines on Ephemeral OS disks. Ephemeral OS disks use local VM capacity rather than remote {azure-short} Storage. This configuration therefore incurs no additional cost and provides lower latency for reading, writing, and reimaging.
You can create a compute machine set running on {azure-first} that deploys machines on Ephemeral OS disks. Ephemeral OS disks use local VM capacity rather than remote {azure-full} Storage. The configuration, therefore, incurs no additional cost and provides lower latency for reading, writing, and reimaging.

[role="_additional-resources"]
.Additional resources

* link:https://docs.microsoft.com/en-us/azure/virtual-machines/ephemeral-os-disks[Ephemeral OS disks for {azure-short} VMs ({azure-full} documentation)]
* link:https://docs.microsoft.com/en-us/azure/virtual-machines/ephemeral-os-disks[Ephemeral OS disks for {azure-short} VMs ({azure-short} documentation)]
9 changes: 5 additions & 4 deletions modules/machineset-creating-azure-ephemeral-os.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,11 +7,13 @@
= Creating machines on Ephemeral OS disks by using compute machine sets

[role="_abstract"]
To improve performance and reduce storage costs, you can host the OS disk directly on the local storage of the virtual machines (VMs) rather than on remote {azure-first} Storage. You can launch machines on Ephemeral OS disks on {azure-short} by editing your compute machine set YAML file.
To improve performance and reduce storage costs, you can host the OS disk directly on the local storage of the virtual machines (VMs) rather than on remote {azure-first} Storage.

You launch machines on Ephemeral OS disks on {azure-short} by editing your compute machine set YAML file.

.Prerequisites

* Have an existing {azure-full} cluster.
* Have an existing {azure-short} cluster.

.Procedure

Expand Down Expand Up @@ -50,7 +52,6 @@ where:
====
The implementation of Ephemeral OS disk support in {product-title} only supports the `CacheDisk` placement type. Do not change the `placement` configuration setting.
====

. Create a compute machine set using the updated configuration:
+
[source,terminal]
Expand All @@ -60,4 +61,4 @@ $ oc create -f <machine-set-config>.yaml

.Verification

* On the {azure-full} portal, review the *Overview* page for a machine deployed by the compute machine set, and verify that the `Ephemeral OS disk` field is set to `OS cache placement`.
* On the {azure-short} portal, review the *Overview* page for a machine deployed by the compute machine set, and verify that the `Ephemeral OS disk` field is set to `OS cache placement`.
2 changes: 1 addition & 1 deletion modules/machineset-customer-managed-encryption-azure.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,4 +39,4 @@ providerSpec:

[role="_additional-resources"]
.Additional resources
* https://docs.microsoft.com/en-us/azure/virtual-machines/disk-encryption#customer-managed-keys[Customer-managed keys ({azure-short} documentation)]
* link:https://docs.microsoft.com/en-us/azure/virtual-machines/disk-encryption#customer-managed-keys[Customer-managed keys ({azure-short} documentation)]
7 changes: 3 additions & 4 deletions modules/machineset-yaml-azure.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,8 +16,7 @@ You can define a machine set YAML to provision nodes by specifying parameters su

The sample YAML defines a compute machine set that runs in the `1` {azure-first} zone in a region and creates nodes that are labeled with
ifndef::infra[`node-role.kubernetes.io/<role>: ""`.]
ifdef::infra[`node-role.kubernetes.io/infra: ""`.]
The YAML file specifies a taint to prevent user workloads from being scheduled on infra nodes. After adding the `NoSchedule` taint on the infrastructure node, existing DNS pods running on that node are marked as `misscheduled`. You must either delete or link:https://access.redhat.com/solutions/6592171[add toleration on `misscheduled` DNS pods].
ifdef::infra[`node-role.kubernetes.io/infra: ""`. The YAML specifies a taint to prevent user workloads from being scheduled on infra nodes. After adding the `NoSchedule` taint on the infrastructure node, existing DNS pods running on that node are marked as `misscheduled`. You must either delete or link:https://access.redhat.com/solutions/6592171[add toleration on `misscheduled` DNS pods].

In the sample, `<infrastructure_id>` is the infrastructure ID label that is based on the cluster ID that you set when you provisioned the cluster, and
ifndef::infra[`<role>`]
Expand Down Expand Up @@ -127,7 +126,7 @@ endif::infra[]

where:

`<infrastructure_id>`:: Specifies the infrastructure ID that is based on the cluster ID that you set when you provisioned the cluster. If you have the OpenShift CLI installed, you can obtain the infrastructure ID by running the following command:
`<infrastructure_id>`:: Specifies the infrastructure ID that is based on the cluster ID that you set when you provisioned the cluster. If you have the {oc-first} installed, you can obtain the infrastructure ID by running the following command:
+
[source,terminal]
----
Expand Down Expand Up @@ -183,4 +182,4 @@ ifeval::["{context}" == "creating-infrastructure-machinesets"]
endif::[]
ifeval::["{context}" == "cluster-tasks"]
:!infra:
endif::[]
endif::[]