Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
103 changes: 103 additions & 0 deletions modules/creating-a-machine-pool-cli-win-li.adoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,103 @@
// Module included in the following assemblies:
//
// * rosa_cluster_admin/rosa_nodes/rosa-managing-worker-nodes.adoc

:_mod-docs-content-type: PROCEDURE
[id="creating_a_machine_pools_cli_win_li_{context}"]
= Creating a machine pool with AWS Windows License Included enabled using the {rosa-cli}

[role="_abstract"]
If you are using {VirtProductName} on a {product-title} cluster running Windows VMs you need to be license-compliant with Microsoft Windows in AWS. The hosts (AWS x86-64 bare metal EC2 instances) running these VMs must be enabled with AWS EC2 Windows License Included (LI).

[IMPORTANT]
====
Enabling AWS Windows LI on a machine pool applies the associated licensing fees on that specific machine pool. This includes billing for the full vCPU allocation of each AWS Windows LI enabled host in your {product-title} cluster. Windows LI enabled machine pools will also deny vCPU over-allocation on {VirtProductName} VMs. For more information, see link:https://aws.amazon.com/windows/resources/licensing//[Microsoft Licensing on AWS] and the link:https://docs.redhat.com/en/documentation/red_hat_openshift_service_on_aws/4/html/introduction_to_rosa/policies-and-service-definition#rosa-hcp-instance-types[{product-title} instance types].
====

.Prerequisites

* You installed and configured the {rosa-cli} version 1.2.58 or above.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* You installed and configured the {rosa-cli} version 1.2.58 or above.
* You installed and configured the {rosa-cli} version 1.2.58 or above.
* You have a cluster at OCP version 4.19 or higher

* You logged in to your Red{nbsp}Hat account using the {rosa-cli}.
* You created a {product-title} cluster version 4.19 or above.
* You identified an x86-64 bare metal EC2 instance type to use {VirtProductName}. For more, see link:https://aws.amazon.com/ec2/instance-types/#Bare_metal[Amazon EC2 Instance Types].
* You are in compliance with Microsoft and AWS requirements for the Microsoft licenses and associated costs.

.Procedure

* To add a Windows LI enabled machine pool to a {product-title} cluster, create the machine pool with the following definitions:
+
[source,terminal]
----
$ rosa create machinepool --cluster=<cluster-name> \
--name=<machine_pool_id> \
--replicas=<replica_count> \
--instance-type=<instance_type> \
--type=<image_type>
----
where:

`--name=<machine_pool_id>`:: Specifies the name of the machine pool. Replace `<machine_pool_id>` with the name of your machine pool.
`--replicas=<replica_count>`:: Specifies the number of compute nodes to provision. If you deployed {product-title} using a single availability zone, this defines the number of compute nodes to provision to the machine pool for the zone. If you deployed your cluster using multiple availability zones, this defines the number of compute nodes to provision in total across all zones and the count must be a multiple of 3. The `--replicas` argument is required when autoscaling is not configured.
`--instance-type=<instance_type>`:: Specifies the instance type. You can only select an x86-64 bare metal instance type to enable Windows LI. For example, you can use `m5zn.metal` or `i3.metal`. You cannot change the instance type for a machine pool after the pool is created.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 [error] RedHat.TermsErrors: Use 'bare-metal instance' rather than 'bare metal instance'. For more information, see RedHat.TermsErrors.

`--type=<type>`:: You must specify `Windows` to ensure the machine pool is created with Windows LI enabled.
Comment thread
AedinC marked this conversation as resolved.
+
The following command creates a Windows LI enabled machine pool called `mymachinepool` using the `m5zn.metal` instance type with 1 compute node replica:
+
[source,terminal]
----
$ rosa create machinepool --cluster=mycluster --name=mymachinepool --type=Windows --instance-type=m5zn.metal --replicas=1
----
+
**Example output**
+
[source,terminal]
----
I: Machine pool 'mymachinepool' created successfully on cluster 'mycluster'
I: To view all machine pools, run 'rosa list machinepools -c mycluster'
----

.Verification
Comment thread
AedinC marked this conversation as resolved.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At the end of this section, can we add a small sentence and link that links to the KCS docs from the CNV team for how to run virtualized windows workloads once a Windows LI node is set up? Documenting how to do that isn't in scope for these openshift docs, but it can help the reader have less clicks to reach that information if they're just starting out using CNV


. List the available machine pools on your cluster by running the following command:
+
[source,terminal]
----
$ rosa list machinepools --cluster=<cluster_name>
----
+
. Describe the information of a specific machine pool in your cluster:
+
[source,terminal]
----
$ rosa describe machinepool --cluster=<cluster_name> --machinepool=mymachinepool
----
+
The output has the image type set to `Windows` as shown in the following example:
+
**Example output**
+
[source,terminal]
----
ID: mymachinepool
Cluster ID: mycluster
Autoscaling: No
Desired replicas: 1
Current replicas: 1
Instance type: m5zn.metal
Image type: Windows
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hunterkepley Would this thing will be shown in rosa describe machinepool command in GA.

Labels:
Tags:
Taints:
Availability zone: us-east-1a
Subnet: <subnet-id>
Disk Size: 300 GiB
Version: 4.19.18
EC2 Metadata Http Tokens: optional
Autorepair: Yes
Tuning configs:
Kubelet configs:
Additional security group IDs:
Node drain grace period:
----
+
. For more information about running virtualized Windows workloads after you have set up a Windows LI enabled machine pool, see link:https://access.redhat.com/solutions/7135149[Creating a Windows VM compliant to AWS EC2 Windows License Included].
18 changes: 2 additions & 16 deletions modules/creating-a-machine-pool-cli.adoc
Comment thread
AedinC marked this conversation as resolved.
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,7 @@
[id="creating_machine_pools_cli_{context}"]
= Creating a machine pool using the {rosa-cli}

[role="_abstract"]
You can create additional machine pools for your {product-title} cluster by using the {rosa-cli-first}.

[NOTE]
Expand Down Expand Up @@ -200,22 +201,6 @@ endif::openshift-rosa-hcp[]
I: To view all machine pools, run 'rosa list machinepools -c mycluster'
----

//ifdef::openshift-rosa-hcp[] Uncomment this out once HCP split occurs
* To add a Windows License Included enabled machine pool to a {product-title} cluster, see link:https://access.redhat.com/articles/7096903[AWS Windows License Included for {product-title}].
+
Windows License Included enabled machine pools can only be created when the following criteria is met:

** The host cluster is a {product-title} cluster.
** The instance type is bare metal EC2.
+
[IMPORTANT]
====
AWS Windows License Included for {product-title} is a Technology Preview feature only. Technology Preview features are not supported with Red{nbsp}Hat production service level agreements (SLAs) and might not be functionally complete. Red{nbsp}Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

For more information about the support scope of Red{nbsp}Hat Technology Preview features, see link:https://access.redhat.com/support/offerings/techpreview/[Technology Preview Features Support Scope].
====
//endif::openshift-rosa-hcp[] Uncomment this out once HCP split occurs

.Verification

You can list all machine pools on your cluster or describe individual machine pools.
Expand Down Expand Up @@ -262,6 +247,7 @@ Cluster ID: 27iimopsg1mge0m81l0sqivkne2qu6dr
Autoscaling: Yes
Replicas: 3-6
Instance type: m5.xlarge
Image type: Windows
Labels: app=db, tier=backend
Taints:
Availability zones: us-east-1a, us-east-1b, us-east-1c
Expand Down
11 changes: 10 additions & 1 deletion modules/creating-a-machine-pool-ocm.adoc
Comment thread
AedinC marked this conversation as resolved.
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,16 @@ endif::openshift-rosa,openshift-rosa-hcp[]
====
You cannot change the instance type for a machine pool after the pool is created.
====

ifdef::openshift-rosa-hcp[]
. Optional: If you are using {VirtProductName} on a {product-title} cluster, you might want to run Windows VMs. In order to be license-compliant with Microsoft Windows in AWS, the hosts (x86-64 bare metal EC2 instances) running these VMs must be enabled with AWS EC2 Windows License Included. To enable the machine pool for AWS Windows License Included, select the *Enable machine pool for AWS Windows License Included* checkbox.
+
You can only select this option when the host cluster is a {product-title} cluster version 4.19 and later and the instance type is x86-64 bare metal EC2.
+
[IMPORTANT]
====
Enabling AWS Windows LI on a machine pool applies the associated licensing fees on that specific machine pool. This includes billing for the full vCPU allocation of each AWS Windows LI enabled host in your {product-title} cluster. Windows LI enabled machine pools will also deny vCPU over-allocation on {VirtProductName} VMs. For more information, see link:https://aws.amazon.com/windows/resources/licensing//[Microsoft Licensing on AWS] and the link:https://docs.redhat.com/en/documentation/red_hat_openshift_service_on_aws/4/html/introduction_to_rosa/policies-and-service-definition#rosa-hcp-instance-types[{product-title} instance types].
====
endif::openshift-rosa-hcp[]
. Optional: Configure autoscaling for the machine pool:
.. Select *Enable autoscaling* to automatically scale the number of machines in your machine pool to meet the deployment needs.
ifdef::openshift-dedicated[]
Expand Down
14 changes: 14 additions & 0 deletions modules/rosa-release-notes-Q1-2026.adoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
// Module included in the following assemblies:
// * rosa-release-notes.adoc

:_mod-docs-content-type: REFERENCE
[id="rosa-q1-2026_{context}"]
= Q1 2026

[role="_abstract"]
The following items were added during the first quarter of 2026.

ifdef::openshift-rosa-hcp[]
* **AWS Windows License Included now available for {product-title}.** You can now add a Windows License Included enabled machine pool to a {product-title} cluster. For more information, see link:https://docs.redhat.com/en/documentation/red_hat_openshift_service_on_aws/4/html/cluster_administration/managing-compute-nodes-using-machine-pools#creating_a_machine_pools_cli_win_li[Creating a machine pool with AWS Windows License Included enabled using the {rosa-cli}].
endif::openshift-rosa-hcp[]

9 changes: 6 additions & 3 deletions modules/rosa-release-notes-Q4-2025.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -5,11 +5,15 @@
[id="rosa-q4-2025_{context}"]
= Q4 2025

[role="_abstract"]
[role="_abstract"]
The following items were added during the fourth quarter of 2025.

ifdef::openshift-rosa-hcp[]
* **AWS Windows License Included now available for {product-title}.** You can now add a Windows License Included enabled machine pool to a {product-title} cluster. For more information, see link:https://docs.redhat.com/en/documentation/red_hat_openshift_service_on_aws/4/html/cluster_administration/managing-compute-nodes-using-machine-pools#creating_a_machine_pools_cli_win_li[Creating a machine pool with AWS Windows License Included enabled using the {rosa-cli}].
endif::openshift-rosa-hcp[]

* ** AWS GovCloud.**
The Amazon Web Services (AWS) GovCloud service is now available and for use by federal and government agencies, or by commercial organizations and Federal Information Security Modernization Act (FISMA) R&D Universities supporting a government contract or in the process of bidding on a government contract such as a request for proposal (RFP) or request for information (RFI) pre-bid stage.
The Amazon Web Services (AWS) GovCloud service is now available and for use by federal and government agencies, or by commercial organizations and Federal Information Security Modernization Act (FISMA) R&D Universities supporting a government contract or in the process of bidding on a government contract such as a request for proposal (RFP) or request for information (RFI) pre-bid stage.
For more information, see
ifdef::openshift-rosa-hcp[]
link:
Expand All @@ -25,7 +29,6 @@ ifdef::openshift-rosa-hcp[]
{product-title} now supports ImageDigestMirrorSets (IDMS), enabling clusters to redirect image pulls to a private, mirrored registry. This critical enhancement means customers in air-gapped or restricted networks can host their own mirrors for third-party images while satisfying strict security and compliance requirements. For more information, see link:https://docs.redhat.com/en/documentation/red_hat_openshift_service_on_aws/4/html-single/images/index#images-registry-mirroring_image-configuration-hcp[Image registry mirroring for {product-title}].
endif::openshift-rosa-hcp[]


* **New version of {product-title} available.** {product-title} version 4.20 is now available for new clusters.

ifdef::openshift-rosa-hcp[]
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -40,6 +40,7 @@ include::modules/creating-a-machine-pool-ocm.adoc[leveloffset=+2]
include::modules/creating-a-machine-pool-cli.adoc[leveloffset=+2]
//OSDOCS-14809: Adding a separate module about Capacity Reservations. This might be a temporary solution since this module largely reuses content from modules/creating-a-machine-pool-cli.adoc. We might consider restructuring content from these 2 modules to meet ContentX and DITA migration goals.
ifdef::openshift-rosa-hcp[]
include::modules/creating-a-machine-pool-cli-win-li.adoc[leveloffset=+2]
include::modules/creating-a-machine-pool-cli-capres.adoc[leveloffset=+2]
endif::openshift-rosa-hcp[]

Expand Down
3 changes: 3 additions & 0 deletions rosa_release_notes/rosa-release-notes.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,9 @@ toc::[]
Find new additions, recent changes, and relevant updates for {product-title} listed below in quarterly increments.

// //remove the conditional if Classic notes are added to the module
ifdef::openshift-rosa-hcp[]
include::modules/rosa-release-notes-Q1-2026.adoc[leveloffset=+1]
endif::openshift-rosa-hcp[]

include::modules/rosa-release-notes-Q4-2025.adoc[leveloffset=+1]

Expand Down