Multiple default storageClasses when specifying storageClass in EKS cluster

When creating an EKS cluster and specifying a custom storage class (e.g. st1), the default gp2 storageClass is created along side the custom st1 storageClass which is also marked as default.

Where storageClass = "st1":

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,
});

This results in:

NAME                                   PROVISIONER             AGE
gp2 (default)                          kubernetes.io/aws-ebs   23m
kafka-cluster-st1-evr2qvmh (default)   kubernetes.io/aws-ebs   21m

This can cause issues when helm charts rely on one default storage class since the storageClass name cannot be passed directly to the charts.

Expected behavior: One storageClass is marked as default after EKS creation (preferably the user specified class) Actual behavior: Both the EKS created gp2 AND the user specified st1 storage class are marked as default.

Other thoughts: Ability to add/remove default status to storageClasses

[metral]

#172 will close out this issue and #139, by supplying the exported names of all storage classes. This can then be used to pass into the Helm charts per the original use-case need.

[lukehoban]

@metral What work is being tracked in this issue now?