[EKS] EBS CSI Driver Incompatibility Between EKS AutoMode and Managed Node Groups

Issue Overview:
-----------------

In an EKS cluster with both AutoMode nodes and Managed Node Groups, we observed a conflict in how nodes register with the EBS CSI driver:
• EKS AutoMode nodes automatically register with ebs.csi.eks.amazonaws.com.
• Managed Node Groups automatically register with ebs.csi.aws.com.
• This mismatch causes PVC provisioning and attachment failures when workloads run across both node types.

Findings:
----------

• EKS AutoMode nodes are tightly coupled with ebs.csi.eks.amazonaws.com, and they do not register with ebs.csi.aws.com.
• Managed Node Groups are tightly coupled with ebs.csi.aws.com, and they do not switch to ebs.csi.eks.amazonaws.com.
• Mixing AutoMode and Managed nodes in the same cluster leads to PVC attachment failures.

Impact:
--------

• Workloads that rely on EBS volumes fail when scheduled across both node types.
• Manual intervention is needed to ensure workloads run on the correct nodes, leading to operational overhead.

Expected Behavior:
---------------------

• Nodes in an EKS cluster should register consistently with the same CSI driver.
• Either both node types should support a unified EBS CSI driver, or there should be a way to configure the CSI driver per cluster.

**Requesting Labels:** EKS, Amazon Elastic Kubernetes Service, EKS Auto Mode, EKS Networking

Start by reviewing the reported EKS setup with both AutoMode nodes and Managed Node Groups, then verify which EBS CSI driver each node registers with. Reproduce PVC provisioning and attachment across both node types. Done means the cluster provides consistent EBS CSI behavior or a documented per-cluster configuration path without manual workload placement.

Written by the indexing model from the issue text.