anyone knows why two default storageclasses got cr...
# general
d
anyone knows why two default storageclasses got created when creating eks cluster?
Copy code
NAME                                                      PROVISIONER             AGE
gp2 (default)                                             <http://kubernetes.io/aws-ebs|kubernetes.io/aws-ebs>   6m
online-sandbox-yding-eks-cluster-gp2-vg7p51nj (default)   <http://kubernetes.io/aws-ebs|kubernetes.io/aws-ebs>   4m
w
What did you pass to
storageClasses:
on your
eks.Cluster
? We should create one storage class per thing you pass there.
d
I didn’t pass anything
This is what I have:
Copy code
const cluster = new eks.Cluster(environment+"-eks-cluster", {
  vpcId             : config.require("vpc-id"),
  subnetIds         : vpcSubnetIds,
  instanceType      : "m4.4xlarge",
  nodePublicKey     : workerNodePublicKey, 
  nodeRootVolumeSize: 200,
  desiredCapacity   : config.requireNumber("desired-nodes"),
  maxSize           : config.requireNumber("max-nodes"),
  minSize           : config.requireNumber("min-nodes"),
  nodeUserData      : userData,
  deployDashboard   : false}
This one is always there
online-sandbox-yding-eks-cluster-gp2-vg7p51nj (default)
but sometimes it’ll create another default
gp2
, sometimes not, I’m not sure why that happens, but I didn’t pass in
storageClasses: "gp2"
this time.
w
Ahh - I see @creamy-potato-29402 just opened https://github.com/pulumi/pulumi-eks/issues/54 noting that there was a change in recent EKS to auto-create the
gp2
storage class. We should likely stop creating a custom GP2 storage class as well on these newer EKS versions.
c
Yep. Will fix as part of the tweaks we’re making to pulumi/eks.
w
Note that I don't think we fixed this particular issue yet - tracked in https://github.com/pulumi/pulumi-eks/issues/54. If this is blocking, we can prioritize getting out a fix.