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.

Pulumi Community

Yeah, query was an experimental thing from a few years back, and doesn’t work as part of a normal Pulumi program. You could use the pulumi-command provider to run a `kubectl` command that returns the info you need formatted as JSON, and it should be fairly straightforward to parse the results. This requires the `kubectl` binary to be available wherever that pulumi program is running, but it’s quite flexible.

That's what I was gonna try next! Thanks. <@UE1LN7A22> 

What if its during the pulumi github action?

I know i can install kubectl, but is it possible to get the pulumi action aware of kubectl if installed? if its dont in another step i think its gone?

pretty sure the workflow context keeps `kubectl` in between steps if you were to install it in a setup step

and i ended up using this: <https://github.com/Azure/setup-kubectl>