You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Starting in Kubernetes v1.17, the in-tree storage plugin was marked as deprecated and it will be removed in EKS v1.23. Users need to install to the EBS CSI driver prior to upgrading to EKS v1.23
Need to find a definitive way of determining if the EBS CSI driver is installed. Straightforward if installed via EKS Addon, less so if users have installed as self-managed (i.e. - Helm chart)
Use case
Starting in Kubernetes
v1.17
, the in-tree storage plugin was marked as deprecated and it will be removed in EKSv1.23
. Users need to install to the EBS CSI driver prior to upgrading to EKSv1.23
The in-tree Amazon EBS storage provisioner is deprecated. If you are upgrading your cluster to version 1.23, then you must first install the Amazon EBS driver before updating your cluster. For more information, see Amazon EBS CSI migration frequently asked questions. If you have pods running on a version 1.22 or earlier cluster, then you must install the Amazon EBS driver before updating your cluster to version 1.23 to avoid service interruption. https://docs.aws.amazon.com/eks/latest/userguide/ebs-csi-migration-faq.html
Solution/User Experience
kubernetes.io/aws-ebsStorageClass
and recommend users update to the new API resource groups provided by the CSIAlternative solutions
The text was updated successfully, but these errors were encountered: