0

After installation of aws-ebs-csi-driver I've realized that there is default in-tree implementation kubernetes.io/aws-ebs which is deprecated according to official doc:

$ kubectl get StorageClass
NAME            PROVISIONER             RECLAIMPOLICY   VOLUMEBINDINGMODE      ALLOWVOLUMEEXPANSION   AGE
ebs-generic     ebs.csi.aws.com         Delete          WaitForFirstConsumer   false                  91s
gp2 (default)   kubernetes.io/aws-ebs   Delete          WaitForFirstConsumer   false                  7h42m

The question is, is it good idea to remove it or at least making newer one as default?
Will further EKS upgrade bring old kubernetes.io/aws-ebs StorageClass again? Is it reasonable at all?

I am using AWS EKS.

Improve this question

0

Reset to default

You must log in to answer this question.

Browse other questions tagged .