Skip to content

BZ2102828: Cu requires guidance on windows container Vs OCP windows node version compatibility and best dev practices to avoid compatibility issues. #49446

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

Closed
wants to merge 1 commit into from
Closed

BZ2102828: Cu requires guidance on windows container Vs OCP windows node version compatibility and best dev practices to avoid compatibility issues. #49446

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
44 changes: 7 additions & 37 deletions _topic_maps/_topic_map.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -252,7 +252,7 @@ Topics:
Topics:
- Name: Preparing to install on IBM Cloud VPC
File: preparing-to-install-on-ibm-cloud
- Name: Configuring an IBM Cloud account
- Name: Configuring an IBM Cloud account VPC
File: installing-ibm-cloud-account
- Name: Configuring IAM for IBM Cloud VPC
File: configuring-iam-ibm-cloud
Expand Down Expand Up @@ -470,8 +470,6 @@ Topics:
File: installing-customizing
- Name: Configuring your firewall
File: configuring-firewall
- Name: Enabling Linux control group version 2 (cgroup v2)
File: enabling-cgroup-v2
- Name: Validating an installation
File: validating-an-installation
Distros: openshift-origin,openshift-enterprise
Expand Down Expand Up @@ -525,8 +523,6 @@ Topics:
File: understanding-openshift-updates
- Name: Understanding upgrade channels
File: understanding-upgrade-channels-release
- Name: Understanding OpenShift update duration
File: understanding-openshift-update-duration
- Name: Preparing to perform an EUS-to-EUS update
File: preparing-eus-eus-upgrade
- Name: Updating a cluster using the web console
Expand All @@ -543,8 +539,6 @@ Topics:
Distros: openshift-enterprise
- Name: Updating hardware on nodes running on vSphere
File: updating-hardware-on-nodes-running-on-vsphere
- Name: Updating a cluster that includes the Special Resource Operator
File: updating-clusters-sro
# - Name: Troubleshooting an update
# File: updating-troubleshooting
---
Expand Down Expand Up @@ -1045,14 +1039,12 @@ Topics:
File: deleting-network-policy
- Name: Defining a default network policy for projects
File: default-network-policy
- Name: Configuring multitenant isolation with network policy
- Name: Configuring multitenant network policy
File: multitenant-network-policy
- Name: AWS Load Balancer Operator
Dir: aws_load_balancer_operator
Distros: openshift-enterprise,openshift-origin
Topics:
- Name: Understanding the AWS Load Balancer Operator
File: understanding-aws-load-balancer-operator
- Name: Installing the AWS Load Balancer Operator
File: install-aws-load-balancer-operator
- Name: Creating an instance of the AWS Load Balancer Controller
Expand Down Expand Up @@ -1763,8 +1755,6 @@ Name: Building applications
Dir: applications
Distros: openshift-enterprise,openshift-origin
Topics:
- Name: Building applications overview
File: index
- Name: Projects
Dir: projects
Topics:
Expand Down Expand Up @@ -1921,8 +1911,6 @@ Topics:
File: adding-aws-compute-user-infra
- Name: Adding compute machines to vSphere
File: adding-vsphere-compute-user-infra
- Name: Adding compute machines to a cluster on RHV
File: adding-rhv-compute-user-infra
- Name: Adding compute machines to bare metal
File: adding-bare-metal-compute-user-infra
- Name: Managing machines with the Cluster API
Expand Down Expand Up @@ -2050,7 +2038,7 @@ Topics:
- Name: Working with containers
Dir: containers
Topics:
- Name: Understanding containers
- Name: Using containers
File: nodes-containers-using
- Name: Using Init Containers to perform tasks before a pod is deployed
File: nodes-containers-init
Expand Down Expand Up @@ -2085,9 +2073,6 @@ Topics:
- Name: Configuring your cluster to place pods on overcommited nodes
File: nodes-cluster-overcommit
Distros: openshift-enterprise,openshift-origin
- Name: Enabling Linux control group version 2 (cgroup v2)
File: nodes-cluster-cgroups-2
Distros: openshift-enterprise,openshift-origin
- Name: Enabling features using FeatureGates
File: nodes-cluster-enabling-features
Distros: openshift-enterprise,openshift-origin
Expand All @@ -2106,7 +2091,6 @@ Topics:
Topics:
- Name: Adding worker nodes to single-node OpenShift clusters
File: nodes-sno-worker-nodes
---
Name: Windows Container Support for OpenShift
Dir: windows_containers
Distros: openshift-origin,openshift-enterprise
Expand Down Expand Up @@ -2249,8 +2233,6 @@ Topics:
File: enabling-alert-routing-for-user-defined-projects
- Name: Managing metrics
File: managing-metrics
- Name: Querying metrics
File: querying-metrics
- Name: Managing metrics targets
File: managing-metrics-targets
- Name: Managing alerts
Expand Down Expand Up @@ -2339,7 +2321,7 @@ Topics:
- Name: Deploying distributed units at scale in a disconnected environment
File: ztp-deploying-disconnected
Distros: openshift-origin,openshift-enterprise
- Name: Requesting CRI-O and Kubelet profiling data by using the Node Observability Operator
- Name: Requesting CRI-O and Kubelet profiling data using the Node Observability Operator
File: node-observability-operator
Distros: openshift-origin,openshift-enterprise
---
Expand Down Expand Up @@ -2397,10 +2379,6 @@ Topics:
File: restoring-applications
- Name: Troubleshooting
File: troubleshooting
- Name: OADP API
File: oadp-api
- Name: Advanced OADP features and functionalities
File: oadp-advanced-topics
- Name: Control plane backup and restore
Dir: control_plane_backup_and_restore
Topics:
Expand Down Expand Up @@ -3234,7 +3212,7 @@ Topics:
- Name: Updating OKD Virtualization
File: upgrading-virt
Distros: openshift-origin
- Name: Security policies
- Name: Additional security privileges granted for kubevirt-controller and virt-launcher
File: virt-additional-security-privileges-controller-and-launcher
- Name: Using the CLI tools
File: virt-using-the-cli-tools
Expand Down Expand Up @@ -3475,20 +3453,14 @@ Topics:
File: virt-exposing-custom-metrics-for-vms
- Name: OpenShift Virtualization critical alerts
File: virt-virtualization-alerts
- Name: Collecting data for Red Hat Support
- Name: Collecting OpenShift Virtualization data for Red Hat Support
File: virt-collecting-virt-data
Distros: openshift-enterprise
- Name: Backup and restore
Dir: backup_restore
Topics:
- Name: Installing and configuring OADP
File: virt-installing-configuring-oadp
- Name: Backing up and restoring virtual machines
File: virt-backup-restore-overview
- Name: Backing up virtual machines
File: virt-backing-up-vms
- Name: Restoring virtual machines
File: virt-restoring-vms
# - Name: Collecting OKD Virtualization data for community report
# File: virt-collecting-virt-data
# Distros: openshift-origin
Expand All @@ -3508,8 +3480,6 @@ Topics:
File: serverless-functions-about
- Name: Event sources
File: knative-event-sources
- Name: Brokers
File: serverless-brokers
- Name: Channels and subscriptions
File: serverless-channels
- Name: Install
Expand Down Expand Up @@ -3567,7 +3537,7 @@ Topics:
- Name: Creating and managing subscriptions
File: serverless-subs
# Brokers
- Name: Creating brokers
- Name: Brokers
File: serverless-using-brokers
# Triggers
- Name: Triggers
Expand Down
10 changes: 9 additions & 1 deletion modules/windows-pod-placement.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,14 @@

Before deploying your Windows workloads to the cluster, you must configure your Windows node scheduling so pods are assigned correctly. Since you have a machine hosting your Windows node, it is managed the same as a Linux-based node. Likewise, scheduling a Windows pod to the appropriate Windows node is completed similarly, using mechanisms like taints, tolerations, and node selectors.

With multiple operating systems, and the ability to run multiple Windows OS variants, in the same cluster, you must map your Windows pods to a base Windows OS variant by using a `RuntimeClass`. For example, if you have multiple Windows nodes running on different Windows Server container versions, the cluster could schedule your Windows pods to an incompatible Windows OS variant. You must have `RuntimeClass` objects configured for each Windows OS variant on your cluster. Using a `RuntimeClass` object is also recommended if you have only one Windows OS variant available in your cluster.
With multiple operating systems, and the ability to run multiple Windows OS variants in the same cluster, you must map your Windows pods to a base Windows OS variant by using a `RuntimeClass`. For example, if you have multiple Windows nodes running on different Windows Server container versions, the cluster could schedule your Windows pods to an incompatible Windows OS variant. You must have `RuntimeClass` objects configured for each Windows OS variant on your cluster. Using a `RuntimeClass` object is also recommended if you have only one Windows OS variant available in your cluster.
Copy link
Contributor Author

@mburke5678 mburke5678 Sep 26, 2022 •
edited
Loading

Choose a reason for hiding this comment

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

PEER REVIEW: The only change in this paragraph ^^ is the removal of a comma in the first line. No other changes.

Copy link
Member

Choose a reason for hiding this comment

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

I know it's beyond the scope of this PR since you just added a comma, but should we say ". . . by using a RuntimeClass object." in the first mention?


For more information, see Microsoft's documentation on link:https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/update-containers#host-and-container-version-compatibility[Host and container version compatibility].

[IMPORTANT]
====
The container base image must be the same Windows OS version and build number that is running on the node where the conainer is to be scheduled.

Also, if you upgrade the Windows nodes from one version to another, for example going from 20H2 to 2022, you must upgrade your container base image to match the new version. For more information, see link:https://learn.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/version-compatibility?tabs=windows-server-2022%2Cwindows-11-21H2[Windows container version compatibility].
====