Merge branch 'mainline' into gdc/no-node-pools

Author: geoffcline

.vscode/asciidoc.code-snippets

@@ -152,16 +152,14 @@
     "NODE_ROOT Section": {
         "prefix": "adoc-topic",
         "body": [
-            "//!!NODE_ROOT <section>",
             "[.topic]",
             "[[${1:page-id},${1:page-id}.title]]",
             "= ${2:page title goes here}",
-            ":info_doctype: section",
             "",
             "include::../attributes.txt[]",
             "",
         ],
-        "description": "Creates a NODE_ROOT section template with topic class and ID"
+        "description": "Creates a section template with topic class and ID"
     },
     "Include with Leveloffset": {
         "prefix": "adoc-inc",

latest/ug/attributes.txt

@@ -6,6 +6,13 @@
 :auto-cli-v2-version: 2.12.3
 :auto-cli-v1-version: 1.27.160
 
+// Kubernetes Versions
+
+:k8s-n: 1.32
+:k8s-n-1: 1.31
+:k8s-n-2: 1.30
+:k8s-n-3: 1.29
+
 // Words Geoffrey often spells wrong or doesn't like to type
 
 :ret: retrieve

latest/ug/automode/api-reference.adoc

@@ -1,7 +1,5 @@
-
 [.topic]
 = EKA Auto Mode API Reference WIP
-:info_doctype: section
 
 :ind: indicate
 :Ind: Indicate

latest/ug/automode/associate-workload.adoc

@@ -1,14 +1,9 @@
-//!!NODE_ROOT <section>
-
 include::../attributes.txt[]
 
 [.topic]
 [[associate-workload,associate-workload.title]]
 = Control if a workload is deployed on EKS Auto Mode nodes
-:info_doctype: section
-:info_title: Control if a workload is deployed on EKS Auto Mode nodes
 :info_titleabbrev: Control workload deployment
-:info_abstract: Control if a workload is deployed on EKS Auto Mode nodes
 
 When running workloads in an EKS cluster with {eam}, you might need to control whether specific workloads run on {eam} nodes or other compute types. This topic describes how to use node selectors and affinity rules to ensure your workloads are scheduled on the intended compute infrastructure.
 

latest/ug/automode/auto-configure-alb.adoc

@@ -1,8 +1,6 @@
-//!!NODE_ROOT <section>
 [.topic]
 [[auto-configure-alb,auto-configure-alb.title]]
 = Create an IngressClass to configure an Application Load Balancer
-:info_doctype: section
 :info_titleabbrev: Create ingress class
 
 include::../attributes.txt[]
@@ -26,6 +24,16 @@ EKS Auto Mode creates and configures Application Load Balancers (ALBs). For exam
 * Kubectl configured to connect to your cluster
 ** You can use `kubectl apply -f <filename>` to apply the sample configuration YAML files below to your cluster.
 
+[NOTE]
+====
+EKS Auto Mode requires subnet tags to identify public and private subnets.
+
+If you created your cluster with `eksctl`, you already have these tags.
+
+Learn how to <<tag-subnets-auto>>. 
+====
+
+
 ## Step 1: Create IngressClassParams
 
 Create an `IngressClassParams` object to specify {aws} specific configuration options for the Application Load Balancer. Use the reference below to update the sample YAML file. 
@@ -41,8 +49,6 @@ spec:
   scheme: internet-facing
 ```
 
-
-
 ## Step 2: Create IngressClass
 
 Create an `IngressClass` that references the {aws} specific configuration values set in the `IngressClassParams` resource. Note the name of the `IngressClass` . In this example, both the `IngressClass` and `IngressClassParams` are named `alb`.

latest/ug/automode/auto-configure-nlb.adoc

@@ -1,8 +1,6 @@
-//!!NODE_ROOT <section>
 [.topic]
 [[auto-configure-nlb,auto-configure-nlb.title]]
 = Use Service Annotations to configure Network Load Balancers
-:info_doctype: section
 :info_titleabbrev: Create service
 
 include::../attributes.txt[]
@@ -13,6 +11,15 @@ When you create a Kubernetes service of type `LoadBalancer` in EKS Auto Mode, EK
 
 EKS Auto Mode handles Network Load Balancer provisioning by default for all services of type LoadBalancer - no additional controller installation or configuration is required. The `loadBalancerClass: eks.amazonaws.com/nlb `specification is automatically set as the cluster default, streamlining the deployment process while maintaining compatibility with existing Kubernetes workloads.
 
+[NOTE]
+====
+EKS Auto Mode requires subnet tags to identify public and private subnets.
+
+If you created your cluster with `eksctl`, you already have these tags.
+
+Learn how to <<tag-subnets-auto>>. 
+====
+
 
 == Sample Service
 

latest/ug/automode/auto-disable.adoc

@@ -1,8 +1,6 @@
-//!!NODE_ROOT <section>
 [.topic]
 [[auto-disable,auto-disable.title]]
 = Disable EKS Auto Mode
-:info_doctype: section
 
 include::../attributes.txt[]
 

latest/ug/automode/auto-elb-example.adoc

@@ -1,12 +1,7 @@
-//!!NODE_ROOT <section>
-
 [.topic]
 [[auto-elb-example,auto-elb-example.title]]
 = Deploy a Sample Load Balancer Workload to EKS Auto Mode
-:info_doctype: section
-:info_title: Deploy a sample load balancer workload to EKS Auto Mode
 :info_titleabbrev: Deploy load balancer workload
-:info_abstract: Deploy a sample load balancer workload to EKS Auto Mode
 
 
 include::../attributes.txt[]
@@ -144,6 +139,15 @@ spec:
   controller: eks.amazonaws.com/alb
 ----
 
+[NOTE]
+====
+EKS Auto Mode requires subnet tags to identify public and private subnets.
+
+If you created your cluster with `eksctl`, you already have these tags.
+
+Learn how to <<tag-subnets-auto>>.
+====
+
 Then create the Ingress resource. Create a file named `05-ingress.yaml`:
 
 [source,yaml]

latest/ug/automode/auto-enable-existing.adoc

@@ -1,12 +1,7 @@
-//!!NODE_ROOT <section>
-
 [.topic]
 [[auto-enable-existing,auto-enable-existing.title]]
 = Enable EKS Auto Mode on an existing cluster
-:info_doctype: section
-:info_title: Enable EKS Auto Mode on an existing cluster
 :info_titleabbrev: Enable on cluster
-:info_abstract: Enable EKS Auto Mode on an existing cluster
 
 include::../attributes.txt[]
 

latest/ug/automode/auto-glossary.adoc

@@ -1,11 +1,7 @@
-//!!NODE_ROOT <section>
 [.topic]
 [[auto-glossary,auto-glossary.title]]
 = Glossary
-:info_doctype: section
-:info_title: Glossary of terms for EKS Auto Mode
 :info_titleabbrev: Glossary
-:info_abstract: Glossary of terms for EKS Auto Mode
 
 
 include::../attributes.txt[]