This message was deleted Pulumi Community #announcements

Join Slack

This message was deleted.

# announcements

sparse-intern-71089

04/01/2019, 5:29 PM

This message was deleted.

creamy-potato-29402

04/01/2019, 5:35 PM

@orange-policeman-59119 have you looked at

k8s.storage.v1.StorageClass.get(...)

orange-policeman-59119

04/01/2019, 5:45 PM

whoaaa

orange-policeman-59119

04/01/2019, 5:45 PM

TY!

orange-policeman-59119

04/01/2019, 5:47 PM

That looks like it returns a concrete StorageClass, no

Output

, what happens if the named storage class doesn't exist?

creamy-potato-29402

04/01/2019, 5:47 PM

get

will fail

orange-policeman-59119

04/01/2019, 5:47 PM

orange-policeman-59119

04/01/2019, 5:48 PM

Is there a non-failing

get

orange-policeman-59119

04/01/2019, 5:48 PM

or, lol, do I try catch it? will that work in the pulumi context or will an error propagate outside of an exception

creamy-potato-29402

04/01/2019, 5:50 PM

not right now — can you tell me a bit more about the scenario?

creamy-potato-29402

04/01/2019, 5:50 PM

is the storage class created by the cloud provider?

orange-policeman-59119

04/01/2019, 5:52 PM

I have a Pulumi stack that I want to deploy to a namespace, which means I should be able to deploy it using a service account that has limited permissions to that namespace. In this case, another stack or a cluster admin may have manually created an

ssd

storage class, and if that exists we ought to use that for persistence. If not, we should fall back to the default by leaving it undefined.

orange-policeman-59119

04/01/2019, 5:54 PM

And yes, the storage class could be created by the cloud provider. GKE does not create an SSD class by default, just a standard HDD backed one. I think Azure creates a standard and a premium SSD backed class (it's been a minute since I've used it), and EKS doesn't define any by default.

Open in Slack

Previous Next