You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: latest/ug/automode/auto-networking.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -90,6 +90,6 @@ For more information, see <<auto-configure-alb>> or <<auto-configure-nlb>>.
90
90
[#dns-consider]
91
91
== CoreDNS
92
92
93
-
EKS Auto Mode does not use the traditional CoreDNS Deployment to provide DNS resolution within the cluster. Rather, Auto Mode nodes utilize CoreDNS running as a system service directly on each node. Given this, if transitioning a traditional EKS Cluster to Auto Mode, you can remove the CoreDNS deployment from your cluster, once your workloads have been moved to the Auto Mode nodes.
93
+
EKS Auto Mode does not use the traditional CoreDNS deployment to provide DNS resolution within the cluster. Instead, Auto Mode nodes utilize CoreDNS running as a system service directly on each node. If transitioning a traditional cluster to Auto Mode, you can remove the CoreDNS deployment from your cluster once your workloads have been moved to the Auto Mode nodes.
94
94
95
95
IMPORTANT: If you plan to maintain a cluster with both Auto Mode and non-Auto Mode nodes, you must retain the CoreDNS deployment. Non-Auto Mode nodes rely on the traditional CoreDNS pods for DNS resolution, as they cannot access the node-level DNS service that Auto Mode provides.
0 commit comments