[OSDOCS#18992] CQA pre-migration for Windows Containers index assembly#115719
[OSDOCS#18992] CQA pre-migration for Windows Containers index assembly#115719maxwelldb wants to merge 1 commit into
Conversation
openshift-ci
Bot
added
the
do-not-merge/work-in-progress
|
Skipping CI for Draft Pull Request. |
openshift-ci
Bot
added
the
size/M
openshift-ci
Bot
removed
the
do-not-merge/work-in-progress
|
🤖 Fri Jul 17 20:07:17 - Prow CI generated the docs preview: https://115719--ocpdocs-pr.netlify.app/openshift-enterprise/latest/windows_containers/index.html |
| = Managing Windows container workloads | ||
|
|
||
| [role="_abstract"] | ||
| With a Red Hat subscription, you can get support for running Windows workloads in {product-title}. Windows instances deployed by the WMCO are configured with the containerd container runtime. For more information, see the xref:../windows_containers/wmco_rn/windows-containers-release-notes.adoc#windows-containers-release-notes[release notes]. |
There was a problem hiding this comment.
🤖 [error] OpenShiftAsciiDoc.NoXrefInModules: Do not include xrefs in modules, only assemblies (exception: release notes modules).
| [role="_abstract"] | ||
| With a Red Hat subscription, you can get support for running Windows workloads in {product-title}. Windows instances deployed by the WMCO are configured with the containerd container runtime. For more information, see the xref:../windows_containers/wmco_rn/windows-containers-release-notes.adoc#windows-containers-release-notes[release notes]. | ||
|
|
||
| You can add Windows nodes either by creating a xref:../windows_containers/creating_windows_machinesets/creating-windows-machineset-aws.adoc#creating-windows-machineset-aws[compute machine set] or by specifying existing Bring-Your-Own-Host (BYOH) Window instances through a xref:../windows_containers/byoh-windows-instance.adoc#byoh-windows-instance[configuration map]. |
There was a problem hiding this comment.
🤖 [error] OpenShiftAsciiDoc.NoXrefInModules: Do not include xrefs in modules, only assemblies (exception: release notes modules).
| Compute machine sets are not supported for bare metal or provider agnostic clusters. | ||
| ==== | ||
|
|
||
| For workloads including both Linux and Windows, {product-title} allows you to deploy Windows workloads running on Windows Server containers while also providing traditional Linux workloads hosted on {op-system-first} or {op-system-base-full}. For more information, see xref:../windows_containers/understanding-windows-container-workloads.adoc#understanding-windows-container-workloads[getting started with Windows container workloads]. |
There was a problem hiding this comment.
🤖 [error] OpenShiftAsciiDoc.NoXrefInModules: Do not include xrefs in modules, only assemblies (exception: release notes modules).
|
|
||
| For workloads including both Linux and Windows, {product-title} allows you to deploy Windows workloads running on Windows Server containers while also providing traditional Linux workloads hosted on {op-system-first} or {op-system-base-full}. For more information, see xref:../windows_containers/understanding-windows-container-workloads.adoc#understanding-windows-container-workloads[getting started with Windows container workloads]. | ||
|
|
||
| You need the WMCO to run Windows workloads in your cluster. The WMCO orchestrates the process of deploying and managing Windows workloads on a cluster. For more information, see xref:../windows_containers/enabling-windows-container-workloads.adoc#enabling-windows-container-workloads[how to enable Windows container workloads]. |
There was a problem hiding this comment.
🤖 [error] OpenShiftAsciiDoc.NoXrefInModules: Do not include xrefs in modules, only assemblies (exception: release notes modules).
|
|
||
| You can create a Windows `MachineSet` object to create infrastructure Windows machine sets and related machines so that you can move supported Windows workloads to the new Windows machines. You can create a Windows `MachineSet` object on multiple platforms. | ||
|
|
||
| You can xref:../windows_containers/scheduling-windows-workloads.adoc#scheduling-windows-workloads[schedule Windows workloads] to Windows compute nodes. |
There was a problem hiding this comment.
🤖 [error] OpenShiftAsciiDoc.NoXrefInModules: Do not include xrefs in modules, only assemblies (exception: release notes modules).
|
|
||
| You can xref:../windows_containers/scheduling-windows-workloads.adoc#scheduling-windows-workloads[schedule Windows workloads] to Windows compute nodes. | ||
|
|
||
| You can xref:../windows_containers/windows-node-upgrades.adoc#windows-node-upgrades[perform Windows Machine Config Operator upgrades] to ensure that your Windows nodes have the latest updates. |
There was a problem hiding this comment.
🤖 [error] OpenShiftAsciiDoc.NoXrefInModules: Do not include xrefs in modules, only assemblies (exception: release notes modules).
|
|
||
| You can xref:../windows_containers/windows-node-upgrades.adoc#windows-node-upgrades[perform Windows Machine Config Operator upgrades] to ensure that your Windows nodes have the latest updates. | ||
|
|
||
| You can xref:../windows_containers/removing-windows-nodes.adoc#removing-windows-nodes[remove a Windows node] by deleting a specific machine. |
There was a problem hiding this comment.
🤖 [error] OpenShiftAsciiDoc.NoXrefInModules: Do not include xrefs in modules, only assemblies (exception: release notes modules).
|
|
||
| You can xref:../windows_containers/removing-windows-nodes.adoc#removing-windows-nodes[remove a Windows node] by deleting a specific machine. | ||
|
|
||
| You can xref:../windows_containers/byoh-windows-instance.adoc#byoh-windows-instance[use Bring-Your-Own-Host (BYOH) Windows instances] to repurpose Windows Server VMs and bring them to {product-title}. BYOH Windows instances benefit users who are looking to mitigate major disruptions in the event that a Windows server goes offline. You can use BYOH Windows instances as nodes on {product-title} 4.8 and later versions. |
There was a problem hiding this comment.
🤖 [error] OpenShiftAsciiDoc.NoXrefInModules: Do not include xrefs in modules, only assemblies (exception: release notes modules).
|
|
||
| You can xref:../windows_containers/removing-windows-nodes.adoc#removing-windows-nodes[remove a Windows node] by deleting a specific machine. | ||
|
|
||
| You can xref:../windows_containers/byoh-windows-instance.adoc#byoh-windows-instance[use Bring-Your-Own-Host (BYOH) Windows instances] to repurpose Windows Server VMs and bring them to {product-title}. BYOH Windows instances benefit users who are looking to mitigate major disruptions in the event that a Windows server goes offline. You can use BYOH Windows instances as nodes on {product-title} 4.8 and later versions. |
There was a problem hiding this comment.
🤖 [error] RedHat.TermsErrors: Use 'in case', 'if', or 'when' rather than 'in the event'. For more information, see RedHat.TermsErrors.
|
|
||
| You can xref:../windows_containers/byoh-windows-instance.adoc#byoh-windows-instance[use Bring-Your-Own-Host (BYOH) Windows instances] to repurpose Windows Server VMs and bring them to {product-title}. BYOH Windows instances benefit users who are looking to mitigate major disruptions in the event that a Windows server goes offline. You can use BYOH Windows instances as nodes on {product-title} 4.8 and later versions. | ||
|
|
||
| You can xref:../windows_containers/disabling-windows-container-workloads.adoc#disabling-windows-container-workloads[disable Windows container workloads] by performing the following: |
There was a problem hiding this comment.
🤖 [error] OpenShiftAsciiDoc.NoXrefInModules: Do not include xrefs in modules, only assemblies (exception: release notes modules).
bd68ab2 to
7962378
Compare
| [role="_abstract"] | ||
| With a Red Hat subscription, you can get support for running Windows workloads in {product-title}. Windows instances deployed by the WMCO are configured with the containerd container runtime. For more information, see the xref:../windows_containers/wmco_rn/windows-containers-release-notes.adoc#windows-containers-release-notes[release notes]. | ||
|
|
||
| You can add Windows nodes either by creating a xref:../windows_containers/creating_windows_machinesets/creating-windows-machineset-aws.adoc#creating-windows-machineset-aws[compute machine set] or by specifying existing Bring-Your-Own-Host (BYOH) Window instances through a xref:../windows_containers/byoh-windows-instance.adoc#byoh-windows-instance[config map]. |
There was a problem hiding this comment.
🤖 [error] OpenShiftAsciiDoc.NoXrefInModules: Do not include xrefs in modules, only assemblies (exception: release notes modules).
|
|
||
| You can xref:../windows_containers/removing-windows-nodes.adoc#removing-windows-nodes[remove a Windows node] by deleting a specific machine. | ||
|
|
||
| You can xref:../windows_containers/byoh-windows-instance.adoc#byoh-windows-instance[use Bring-Your-Own-Host (BYOH) Windows instances] to repurpose Windows Server VMs and bring them to {product-title}. BYOH Windows instances benefit users who are looking to mitigate major disruptions if a Windows server goes offline. You can use BYOH Windows instances as nodes on {product-title} 4.8 and later versions. |
There was a problem hiding this comment.
🤖 [error] OpenShiftAsciiDoc.NoXrefInModules: Do not include xrefs in modules, only assemblies (exception: release notes modules).
|
@maxwelldb: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
maxwelldb
added
the
merge-review-needed
3 participants
Version(s): 4.20+
Issue: OSDOCS-18992
Link to docs preview: 4.20+
QE review:
Additional information: One of 3 PRs splitting OSDOCS-18992 (index.adoc CQA pre-migration) by assembly.
Since this is resolving an index.adoc navigation file, xrefs are allowed in the resulting reference modules. These reference modules must only ever be included in one location.