From be1f5231b337c183598e175e3d0e159897a444a7 Mon Sep 17 00:00:00 2001 From: Devansh Popli Date: Thu, 16 Oct 2025 21:59:29 +0530 Subject: [PATCH] Remove note about IAM role usage for Windows nodes --- latest/ug/clusters/windows-support.adoc | 1 - 1 file changed, 1 deletion(-) diff --git a/latest/ug/clusters/windows-support.adoc b/latest/ug/clusters/windows-support.adoc index c9074aa0..e261da5c 100644 --- a/latest/ug/clusters/windows-support.adoc +++ b/latest/ug/clusters/windows-support.adoc @@ -21,7 +21,6 @@ Before deploying Windows nodes, be aware of the following considerations. * You can use host networking on Windows nodes using `HostProcess` Pods. For more information, see https://kubernetes.io/docs/tasks/configure-pod-container/create-hostprocess-pod/[Create a Windows HostProcessPod] in the Kubernetes documentation. * Amazon EKS clusters must contain one or more Linux or Fargate nodes to run core system Pods that only run on Linux, such as CoreDNS. * The `kubelet` and `kube-proxy` event logs are redirected to the `EKS Windows` Event Log and are set to a 200 MB limit. -* You can't use the same IAM role for both Linux and Windows nodes. * You can't use <> with Pods running on Windows nodes. * You can't use <> with Windows nodes. * You can't use `IPv6` with Windows nodes.