docs: DOC-2030: Add K8s Compatability Note re: AWS EKS AMI IDs (#7349)

* Adding k8s compatibility

* Empty commit to trigger Netlify preview

* ci: auto-formatting prettier issues

---------

Co-authored-by: achuribooks <[email protected]>

Author: achuribooks

docs/docs-content/clusters/public-cloud/aws/eks.md

@@ -294,7 +294,7 @@ an AWS account. This section guides you on how to create an EKS cluster in AWS t
     | **Instance Option**                          | Choose a pricing method:<br /><br />- **On-Demand** - Provides stable and uninterrupted compute capacity at a higher cost.<br />- **Spot** - Allows you to bid for unused EC2 capacity at a lower cost.<br />We recommend you base your choice on your application's requirements.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
     | **Instance Type**                            | Select the instance type to use for all nodes in the node pool.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
     | **Amazon Machine Image (AMI) Type**          | Specify a base AMI to use for your worker nodes: **AL2_x86_64**, **AL2_x86_64_GPU**, **AL2023_x86_64_STANDARD**, **AL2023_x86_64_NEURON**, or **AL2023_x86_64_NVIDIA**. An **AL2_x86_64** AMI is used by default if no AMI is selected. <br /><br /> The AMI type cannot be modified post-deployment. Nodes using an Amazon Linux 2023 (AL2023) AMI must configure IAM Roles for Service Accounts (IRSA) if you are using AWS CSI packs such as Amazon EBS CSI, Amazon EFS CSI, and Amazon Cloud Native. IRSA is also required if using the AWS Application Loadbalancer. Refer to the [Scenario - PV/PVC Stuck in Pending Status for EKS Cluster Using AL2023 AMI](../../../troubleshooting/cluster-deployment.md#scenario---pvpvc-stuck-in-pending-status-for-eks-cluster-using-al2023-ami) troubleshooting guide for further information. |
-    | **Enable Nodepool Customization (Optional)** | Activate additional node pool customization options: <br /><br />- **Amazon Machine Image (AMI) ID (Optional)** - Use a pre-configured VM image by providing the ID value of the AMI. The AMI ID can be updated post-deployment, but the base AMI type must always match the type specified in the **Amazon Machine Image (AMI) Type** field. <br />- **Disk Type (Optional)** - Specify the disk type to use.                                                                                                                                                                                                                                                                                                                                                                                                                               |
+    | **Enable Nodepool Customization (Optional)** | Activate additional node pool customization options: <br /><br />- **Amazon Machine Image (AMI) ID (Optional)** - Use a pre-configured VM image by providing the ID value of the AMI. The AMI ID can be updated post-deployment, but the base AMI type must always match the type specified in the **Amazon Machine Image (AMI) Type** field, and the AMI must be compatible with the Kubernetes version specified in the [cluster profile](../../../profiles/cluster-profiles/cluster-profiles.md). <br />- **Disk Type (Optional)** - Specify the disk type to use.                                                                                                                                                                                                                                                                        |
     | **Root Disk size (GB)**                      | Choose a disk size based on your requirements. The default size is `60`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
 
     #### Fargate Profiles