Docker in Production Track

1. Deep Debroy
Software Engineer, Docker Inc.
Kubernetes on Windows
with Docker EE
Taylor Brown
Principal PM Manager, Microsoft
@taylorb_msft

2. Docker EE offers lots of choice
Operating
Systems
[Windows, Linux]
CPU
Architectures
[x86, Mainframe]
Languages
[java, .Net, python, ...]
Environments
[cloud, bare-metal, edge]
Plugins
[storage, networking, logging]
Orchestrators
[swarm, kubernetes]
Software
Architectures
[microservices, monolithic]

3. Why Kubernetes on Docker EE?
Gain operational agility with simplified and secure cluster management
❏Use Kubernetes and Swarm interchangeably
❏Secure application zones with RBAC and resource collections
Build a secure software supply chain
❏Common “source of truth” across Swarm and Kubernetes
❏Globally consistent

4. Why Kubernetes on Windows Server?

5. Why Kubernetes on Windows Server?
35 Certified Kubernetes Distributions

6. Why Kubernetes on Windows Server?
22 Certified Kubernetes Hosting Platforms

7. Why Kubernetes on Windows Server?
49 Certified Kubernetes Service Providers

8. v
Demo

9. Docker EE Architecture
Manager ManagerManager
Worker Worker Worker Worker
Universal Control Plane
Trusted Registry
Data center network fabric
Data center storage fabric
Cloud
Management

10. Kubernetes Architecture
❏Cluster controllers and schedulers
❏Container runtime [CRI]
❏Container networking [CNI]
❏Container storage [FlexVolume + CSI]
❏Logging
❏Monitoring

11. Kubelet on Windows
Linux Kernel
runC (OCI)
Docker Engine
Docker Shim (CRI)
Kubelet

12. Kubelet on Windows
Linux Kernel
runC (OCI)
Docker Engine
Docker Shim (CRI)
Kubelet
Windows Kernel
Host Compute Service(s)
Docker Engine
Docker Shim (CRI)
Kubelet

13. Under development
Kubelet on Windows
Linux Kernel
runC (OCI)
Docker Engine
Docker Shim (CRI)
Kubelet
Windows Kernel
Host Compute Service(s)
Docker Engine
Docker Shim (CRI)
Kubelet
Windows Kernel
Host Compute Service(s)
runHCS (OCI)
containerD (CRI)
Kubelet

14. Kubernetes networking architecture
Pod
vNIC
kubelet
CNI module
Pod
vNIC
Pod
vNIC
Pod
vNIC
Pod
vNIC | vEth
IPAM module
iptables
HNS
Cloud Network
Management
Data center network fabric
kube
proxy
HCS Shim
netns
Host
Network
cloud
provider

15. Docker EE Network configuration
Azure Non-Azure
Linux Calico CNI with Azure VNets Calico CNI with IP-IP tunnels
Windows Azure-vnet-CNI with Azure VNets WinCNI, others ...

16. Windows networking architecture
on Azure
Pod
kubelet
HCS shim
HNS + HCS
Azure-VNET-
CNI
WinCNI
vNIC
vSwitch
L2 bridge
pNIC
CNI
Pod
vNIC
kube
proxy
Azure
IPAM
Load balancer configuration
IP Management

17. Kubernetes storage architecture
Pod
kubelet
CSI module
Pod
Host OS stack
Cloud Storage
Management
Data center storage fabric
In-tree
drivers
Host networking stack
Flexvol module
PV PV
PV Claim PV Claim

18. Docker EE storage configuration
for Windows
In-tree FlexVolume
Block AzureDisk (and others) iSCSI
Shared FS AzureFile (and others) SMB
CSI based external modules for Windows coming in the future

19. Logging on Windows
● Traditionally Windows Server apps write to the Windows event log
● Most linux apps/containers log to stdout (or did…)
So what to do?
● Shim or update
● FluentD, Sysdig etc….

20. Metrics on Windows
● Metrics on Windows for containers are mostly the same as Linux
○ i.e. CRI’s report metrics (CPU/Mem…)
● Windows has multiple ways to expose host perf
○ Agents like Prometheus Node Exporter have limited support

21. ● Microsoft and Docker are working together
to enable your dockerized Windows
workloads run while leveraging all the
features of Kubernetes and Docker EE
combined
● Docker EE builds upon the core
infrastructure work done by the
Kubernetes community
● Join the sig-windows group if you’re
interested in Kubernetes on Windows
In Summary