No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

EKS automatically installs a GP2 storage class now.  Is that the one you are seeing?

<https://docs.aws.amazon.com/eks/latest/userguide/storage-classes.html>

Until recently, we were also generating another copy of the same storage class (because older clusters needed it), but I believe we removed that in <https://github.com/pulumi/pulumi-eks/pull/136> (we may not have yet done a package release after that was merged though).

If you try out `"@pulumi/eks": "dev"` in your package.json, you should be able to see whether that fix will address this for you.

This is what I was seeing:
```&gt; kubectl get storageclasses
NAME                                   PROVISIONER             AGE
gp2 (default)                          <http://kubernetes.io/aws-ebs|kubernetes.io/aws-ebs>   23m
kafka-cluster-st1-evr2qvmh (default)   <http://kubernetes.io/aws-ebs|kubernetes.io/aws-ebs>   21m```

Having the `gp2` class is fine, just the fact that both are marked as default can cause issues.
I’ll try it out, thanks

<@UB3BGTV63> One other thing, is there a way to get the storage class name via the pulumi/kubernetes api?

Used the `dev` version of eks and still got both storage classes marked as `default`

Hmm - could you open an issue in pulumi-eks?  Will need to have someone look into it deeper.

It's quite possible that the default storage class that EKS adds automatically for you on &gt;=1.11 gets auotmatically set as `(default)` - which would make it hard to change that default.  We'll need to look at what we can do about that (and whether that is what's happening here).