When creating an EKS cluster, I specified the storage class type as

st1

. It seems that both a

gp2

AND my

st1

storageClasses get created and they are both marked as

default

. Is this expected behavior? Is there a specific property I need to set to prevent that from happening?

// Create a VPC for our cluster.
const vpc = new awsx.ec2.Vpc("Kafka-VPC", {numberOfAvailabilityZones: 3});

// Create an EKS cluster with the given configuration.
const cluster = new eks.Cluster("kafka-cluster", {
    vpcId: vpc.id,
    subnetIds: vpc.privateSubnetIds,
    instanceType: instanceType,
    desiredCapacity: desiredCapacity,
    minSize: minSize,
    maxSize: maxSize,
    storageClasses: storageClass,
    deployDashboard: deployDashboard,
});

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).

This is what I was seeing:

> 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

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 >=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).

Will do