Windows Machine Config Operator (WMCO) 6.0.0 available on OpenShift 4.11 will move from Windows Server configured with Docker runtime to Windows Server configured with containerd runtime. You can read more about Dockershim deprecation here. Switching from Docker to containerd runtime is relatively easy, and will have better performance and lower overhead. Because the Docker runtime is deprecated in Kubernetes 1.24, containerd is now the default runtime for WMCO-supported Windows nodes. Upon the installation of or an upgrade to WMCO 6.0.0, containerd is installed as a Windows service. The kubelet will now uses containerd for image pulls and as the container runtime instead of the Docker runtime.
Steps to configure containerd for Running Windows Container Workloads on OpenShift.
Install OpenShift 4.11
Follow these steps to install OpenShift Container Platform. Be sure the following pre-requisites documented here are followed.
Prerequisites
- You have access to an OpenShift Container Platform cluster using an account with
cluster-admin
permissions. - You have installed the OpenShift CLI (
oc
). - You have installed your cluster on a supported platform using installer-provisioned infrastructure, or using user-provisioned infrastructure with the
platform: none
field set in yourinstall-config.yaml
file. - You have configured hybrid networking with OVN-Kubernetes for your cluster. This must be completed during the installation of your cluster. For more information, see Configuring hybrid networking.
Install Windows Machine Config Operator 6.0.0
You can install the Windows Machine Config Operator using either the web console or OpenShift CLI (oc
). Refer to product documentation for steps on how to install WMCO from the inCluster Operator Hub.
Be sure that the Windows Machine Config Operator is installed under Installed Operators
.
Configure an instance using Windows MachineSets
You can create a Windows MachineSet
object to serve a specific purpose in your OpenShift Container Platform cluster. For example, you might create infrastructure Windows machine sets and related machines so that you can move supporting Windows workloads to the new Windows machines. Here is a sample YAML that defines a Windows MachineSet object running on Microsoft Azure that the Windows Machine Config Operator (WMCO) can react upon. Please refer to the product documentation for the exact steps for configuring a Windows instance for your platform.
apiVersion: machine.openshift.io/v1beta1
kind: MachineSet
metadata:
labels:
machine.openshift.io/cluster-api-cluster: <infrastructure_id>
name: <windows_machine_set_name>
namespace: openshift-machine-api
spec:
replicas: 1
selector:
matchLabels:
machine.openshift.io/cluster-api-cluster: <infrastructure_id>
machine.openshift.io/cluster-api-machineset: <windows_machine_set_name>
template:
metadata:
labels:
machine.openshift.io/cluster-api-cluster: <infrastructure_id>
machine.openshift.io/cluster-api-machine-role: worker
machine.openshift.io/cluster-api-machine-type: worker
machine.openshift.io/cluster-api-machineset: <windows_machine_set_name>
machine.openshift.io/os-id: Windows
spec:
metadata:
labels:
node-role.kubernetes.io/worker: ""
providerSpec:
value:
apiVersion: azureproviderconfig.openshift.io/v1beta1
credentialsSecret:
name: azure-cloud-credentials
namespace: openshift-machine-api
image:
offer: WindowsServer
publisher: MicrosoftWindowsServer
resourceID: ""
sku: 2022-datacenter
version: latest
kind: AzureMachineProviderSpec
location: <location>
managedIdentity: <infrastructure_id>-identity
networkResourceGroup: <infrastructure_id>-rg
osDisk:
diskSizeGB: 128
managedDisk:
storageAccountType: Premium_LRS
osType: Windows
publicIP: false
resourceGroup: <infrastructure_id>-rg
subnet: <infrastructure_id>-worker-subnet
userDataSecret:
name: windows-user-data
namespace: openshift-machine-api
vmSize: Standard_D2s_v3
vnet: <infrastructure_id>-vnet
zone: "<zone>"
Examine installed configured container runtime
From the command line, type oc get nodes -o wide
code> and observe the output. You should be able to see that containerd is configured as the container runtime for the Windows node.
Upgrading from earlier versions of OpenShift and WMCO
The procedure for an upgrade that includes migration to containerd follows the regular upgrade process.
Run a sample workload
Deploy a sample application to the cluster and be surethe pod is running. Expose the application as a service.
Expand Networking->Services->Name of your service to note the external load balancer location as highlighted below.
Hit that endpoint from a browser to be sure you can access the application.
About the authors
More like this
Browse by channel
Automation
The latest on IT automation that spans tech, teams, and environments
Artificial intelligence
Explore the platforms and partners building a faster path for AI
Open hybrid cloud
Explore how we build a more flexible future with hybrid cloud
Security
Explore how we reduce risks across environments and technologies
Edge computing
Updates on the solutions that simplify infrastructure at the edge
Infrastructure
Stay up to date on the world’s leading enterprise Linux platform
Applications
The latest on our solutions to the toughest application challenges
Original shows
Entertaining stories from the makers and leaders in enterprise tech
Products
- Red Hat Enterprise Linux
- Red Hat OpenShift
- Red Hat Ansible Automation Platform
- Cloud services
- See all products
Tools
- Training and certification
- My account
- Developer resources
- Customer support
- Red Hat value calculator
- Red Hat Ecosystem Catalog
- Find a partner
Try, buy, & sell
Communicate
About Red Hat
We’re the world’s leading provider of enterprise open source solutions—including Linux, cloud, container, and Kubernetes. We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.
Select a language
Red Hat legal and privacy links
- About Red Hat
- Jobs
- Events
- Locations
- Contact Red Hat
- Red Hat Blog
- Diversity, equity, and inclusion
- Cool Stuff Store
- Red Hat Summit