In this self-paced exercise, you will learn how to configure and deploy an Amazon EKS cluster with a Managed Node Group based on Windows. You will then deploy a Windows workload on the cluster and validate it is running.
What Will You Do by Part¶
|Part||What will you do?|
|1||Provision an Amazon EKS Cluster with Windows Node Group|
|2||Deploy a Windows Workload|
|3||Deprovision the EKS cluster|
Architecture & Design¶
- It is recommended to create a "dedicated managed node group" for system level resources while then using a managed node group to run non-system level workloads.
- This configuration allows system level resources to take advantage of the consistency of on-demand or reserved instances and a seperate Windows Node Group to run Windows workloads.
In This exercise, we will create an EKS cluster that contains two (2) managed node groups, one for system resources and the other with a Windows Node Group for workloads. A visual representation of this cluster design is shown below.
flowchart LR subgraph DATA[EKS Data Plane] direction TB subgraph NG1[System Node Group] direction RL i1[Rafay Operator] end subgraph NG2[Windows Node Groups] direction RL f1[Workloads] end end CP[EKS Control Plane] <-.-> DATA
- You have access to an Amazon AWS account with privileges to create an IAM Role with the default Full IAM Policy to allow provisioning of resources on your behalf as part of the EKS cluster lifecycle.
- You have downloaded the RCTL CLI
- You have initialized the RCTL CLI
The instructions describe the process using a combination of the RCTL CLI and the web console. The same steps can be performed using the REST APIs or a Terraform provider for automation.