AWS eks documentation change
Summary
Added workshop promotion tip and corrected AWS console reference typo
Security assessment
Changes include adding a promotional workshop link and fixing a typo ('aws' to 'AWS'). These are editorial improvements with no security implications or security documentation additions.
Diff
diff --git a/eks/latest/best-practices/automode.md b/eks/latest/best-practices/automode.md index 776d33900..f2e773470 100644 --- a//eks/latest/best-practices/automode.md +++ b//eks/latest/best-practices/automode.md @@ -8,0 +9,4 @@ Reasons to use Auto ModeFAQ +###### Tip + +Interested in gaining hands-on experience with Amazon EKS Auto Mode? Join an upcoming virtual Kubernetes workshop led by AWS experts by signing up on [AWS Connected Community](https://aws-experience.com/emea/smb/events/series/simplifying-kubernetes-operations-with-amazon-eks-auto-mode?trk=e3d0398c-e0e9-4665-af82-a2e8124a6db8). + @@ -111 +115 @@ Because AMI customization is not supported, if you have a need for host-level so -If you create a cluster with eksctl or the {aws} console, the only pods running in an EKS Auto Mode cluster are Kubernetes Metrics Server pods. The other components of EKS Auto Mode like Karpenter, the AWS Load Balancer Controller, and the EBS CSI Driver are all running and managed off-cluster. +If you create a cluster with eksctl or the AWS console, the only pods running in an EKS Auto Mode cluster are Kubernetes Metrics Server pods. The other components of EKS Auto Mode like Karpenter, the AWS Load Balancer Controller, and the EBS CSI Driver are all running and managed off-cluster.