~/ nmadiraju.com Amazon EKS · Windows containers
arrow_back Back to nmadiraju
Visual Walkthrough · Amazon EKS nodes

How Windows Containers Work on Amazon EKS

Follow orders-legacy, a .NET Framework app, onto Windows nodes next to Linux services, then check yourself with 8 questions.

1Visual Walkthrough

An EKS cluster with Linux and Windows managed node groups, the VPC resource controller and gMSA sign-in A VPC with two node groups: ng-linux (linux-1, linux-2 on Amazon Linux 2023) and ng-windows (win-1, win-2 on Windows Server 2022 Core). Amazon ECR holds the orders-legacy image. The EKS control plane holds the API server, the VPC resource controller that assigns Windows Pod IPs, and a GMSACredentialSpec. Secrets Manager and Active Directory with SQL Server sit outside the cluster. The walkthrough shows a Windows image failing on Linux, adding Windows nodes, steering Pods by OS, an OS version mismatch, Pod IP limits, and domainless gMSA. You kubectl · aws eks Amazon ECR orders-legacy: windows/amd64 image only YOUR VPC · CLUSTER shop-prod ng-linux · AL2023 ng-windows · SERVER 2022 linux-1 · m6i.large Amazon Linux 2023 kubernetes.io/os=linux linux-2 · m6i.large Amazon Linux 2023 kubernetes.io/os=linux win-1 · m5.large Server 2022 Core build 10.0.20348 win-2 · m5.large Server 2022 Core build 10.0.20348 AMAZON EKS · RUN BY AWS API server · scheduler VPC resource controller hands out Windows Pod IPs GMSACredentialSpec orders-gmsa gMSA: svc-orders$ · secret: orders-ad-user CRD + webhook you install (windows-gmsa) Secrets Manager orders-ad-user portable AD user Active Directory corp.example.com SQL Server orders-db Windows auth only

    2Quiz to check understanding

    Check yourself