Closed tabern closed 1 year ago
Would the recent launch template support on the managed node group resolve/close this roadmap?
Managed Node Group (MNG) with Custom Launch Template does not support Windows at the moment.
This is due to following reasons,
EKS MNG does not add eks:kube-proxy-windows
Kubernetes Group access for Windows worker nodes in 'aws-auth' ConfigMap
system:bootstrappers
and system:nodes
Groups at the moment.eks:kube-proxy-windows
Group in EKS is binded to system:node-proxier
ClusterRole.
system:node-proxier
ClusterRole allows access to Kubernetes API resources Endpoints, Services and Nodes that are required for node bootstrapping purposes.Windows nodes take more boostrapping time than linux nodes. Due to this, EKS MNG fails to add below custom labels (EKS restricted) to worker node
eks.amazonaws.com/nodegroup=<MNG_NAME>
eks.amazonaws.com/nodegroup-image=<AMI_ID>
eks.amazonaws.com/sourceLaunchTemplateId=<LAUNCH_TEMPLATE_ID>
eks.amazonaws.com/sourceLaunchTemplateVersion=<LAUNCH_TEMPLATE_VERSION>
I'd really like managed Windows nodes? Any progress here?
any update on managed windows workers node group?
Hello is there any ETA on managed node groups supporting windows?
How is the WIP going? Should we expect this to be "coming soon" in 2022?
Any news ?
@akestner It looks like this is a well watched issue. Is there anything that you can tell us?
This is a highly requested feature. Would love to see this in 2023.
EKS now supports Windows containers in managed node groups!
What is this Ability to launch Managed Node Groups using EKS-optimized Windows AMIs.
What is the problem? Today, EKS Managed Node Groups support EKS-Optimized Linux AMIs. Windows support will make it easier to run Windows clusters on Amazon EKS.