This message was deleted.

sparse-intern-71089

03/25/2020, 4:05 PM

This message was deleted.

gorgeous-egg-16927

03/25/2020, 4:08 PM

PriorityClass

is a cluster-scoped Kind, so it doesn’t include a namespace. It seems like the error message isn’t very helpful, but try removing the namespace value and see if that fixes it

crooked-helicopter-55521

03/25/2020, 4:09 PM

oh, huh, Ill give that a shot. I originally had no namespace and got the same error so I tried adding it.

crooked-helicopter-55521

03/25/2020, 4:11 PM

yeah, same thing

gorgeous-egg-16927

03/25/2020, 4:11 PM

Ah, I think this is actually a bug with the List type. Can you file an issue on the pulumi-kubernetes repo with that code snippet and error message?

crooked-helicopter-55521

03/25/2020, 4:12 PM

interesting, yup, will do. Thanks for the quick look

gorgeous-egg-16927

03/25/2020, 4:12 PM

You should be able to work around it by creating the

PriorityClass

directly without the enclosing

PriorityClassList

crooked-helicopter-55521

03/25/2020, 4:12 PM

nice, will give that a shot

crooked-helicopter-55521

03/25/2020, 4:26 PM

https://github.com/pulumi/pulumi-kubernetes/issues/1045

billowy-army-68599

03/25/2020, 4:38 PM

this seems related to https://github.com/pulumi/pulumi-kubernetes/issues/1043 as well?

crooked-helicopter-55521

03/25/2020, 4:39 PM

huh, maybe, I'm not familiar enough to really know, but that seems to be on the read side instead of the write

3 Views

Open in Slack

Previous Next

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.