Windows in an OpenShift world
summary
OpenShift is extended to run Windows Server 2019 process-isolated containers using a bring-your-own-host model: an Ansible playbook copies a Windows Machine Config Bootstrapper plus kubelet, kube-proxy, CNI plugins and a Microsoft hybrid-overlay binary onto the Windows VM, configures kubelet as a service, approves CSRs and sets taints for Windows scheduling. Images must match host OS (LTSC 2019), kube-proxy is required on Windows, large base images need pre-pulling, the live demo fails at hybrid-overlay, and an operator-based rollout is planned.
AI-written summary · about
chapters (10)
- 0:00Start
- 1:04Types of Windows Containers
- 5:26Windows Container Images
- 10:44Initial Target
- 15:03Windows Machine Contig Bootstrapper
- 17:15Windows Scale Up Playbook
- 24:31Demo
- 25:33Next Steps
- 27:20Operator Architecture
- 48:40Windows Server Evolution
related talks
37mWindows SIG
36mDeep Dive of Windows Containers on Kubernetes
37mDemo of Kubernetes on Windows Server
31mKubernetes on Windows - A Journey
27mSimplifying Windows Runtime and Deployment in Kubernetes
23mWindows Containers in Kubernetes and a...
37mContainer Technology Drives Windows Application Transformation
01h 04mIntro + Deep Dive: Windows SIG
