AWS eks documentation change
Summary
Clarified requirements for EKS Auto Mode storage classes and removed deprecated PodSecurityPolicy reference
Security assessment
The change removes references to PodSecurityPolicy (a deprecated Kubernetes security feature), but does not indicate a specific security vulnerability being addressed. The update appears to reflect documentation maintenance rather than responding to a security issue. The storage class clarification improves operational accuracy but doesn't introduce security controls.
Diff
diff --git a/eks/latest/userguide/ebs-csi.md b/eks/latest/userguide/ebs-csi.md index 934a46d20..93567b543 100644 --- a//eks/latest/userguide/ebs-csi.md +++ b//eks/latest/userguide/ebs-csi.md @@ -31 +31 @@ The [Amazon Elastic Block Store (Amazon EBS) Container Storage Interface (CSI) d - * Only platform versions created from a storage class using `ebs.csi.eks.amazonaws.com` as the provisioner can be mounted on nodes created by EKS Auto Mode. Existing platform versions must be migrated to the new storage class using a volume snapshot. + * EKS Auto Mode requires storage classes to use `ebs.csi.eks.amazonaws.com` as the provisioner. The standard Amazon EBS CSI Driver (`ebs.csi.aws.com`) manages its own volumes separately. To use existing volumes with EKS Auto Mode, migrate them using volume snapshots to a storage class that uses the Auto Mode provisioner. @@ -52,2 +51,0 @@ To use the snapshot functionality of the Amazon EBS CSI driver, you must first i - * If you’re using a cluster wide restricted [PodSecurityPolicy](./pod-security-policy.html), make sure that the add-on is granted sufficient permissions to be deployed. For the permissions required by each add-on Pod, see the [relevant add-on manifest definition](https://github.com/kubernetes-sigs/aws-ebs-csi-driver/tree/master/deploy/kubernetes/base) on GitHub. -