https://pulumi.com logo
Powered by
d

damp-book-35965

03/14/2019, 5:24 PM
When deploying a new EKS cluster, I see two default storage classes created. One of them is from pulumi..other is from AWS I think. I had to patch the storage class to make it non default by hand. Do I need to do something in the config to ensure only one default exists ?
Copy code
mac-nshah:nshah-pulumi-eks nshah$ kubectl get <http://storageclasses.storage.k8s.io|storageclasses.storage.k8s.io>
NAME                                           PROVISIONER             AGE
gp2 (default)                                  <http://kubernetes.io/aws-ebs|kubernetes.io/aws-ebs>   52m
nshah-test-eks-pulumi-gp2-dtx905hi (default)   <http://kubernetes.io/aws-ebs|kubernetes.io/aws-ebs>   50m
c

creamy-potato-29402

03/14/2019, 6:08 PM
cc @microscopic-florist-22719 I thought we fixed this? wasn’t this the “redundant storage class” bug?
d

damp-book-35965

03/14/2019, 10:01 PM
This is in running the latest version:
Copy code
mac-nshah:nshah-pulumi-eks nshah$ pulumi version
v0.17.1
c

creamy-potato-29402

03/14/2019, 11:47 PM
we did not get around to it this sprint, but I believe we likely will in the next couple weeks.
The pulumi versino does not matter, but the EKS package version does.
d

damp-book-35965

03/14/2019, 11:56 PM
Okay..thanks for letting me know
5 Views
Powered by