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

Can you share your code? Are you including the namespace in the resource name?

<@UCU9C7W73> - the issue is the .get() fails on an initial run... my hope is to create the secret if it doesn't exist, or get it (and the contents as outputs) if it does, and reuse the contents.  Essentially using kubernetes secrets as pulumi secrets, but with the added step of creating the random values if it doesn't

<@U02R4GEUAUE> - i will look into the random.RandomPassword w/ keepers, but i was hoping to not have the RNG seeded with anything so the only way to know the password is to have access to the k8s secret.

<@U02EBGD61HU> The query API might be better suited for that: <https://www.pulumi.com/blog/query-kubernetes/>

but IMO, that workflow seems dangerous. I'd probably use `pulumi import` to bring the secret under Pulumi management

<@UCU9C7W73> - it would ideally be initially created by pulumi... i just want the ability to pull existing values (if they exist) and create them if they don't.

the query api looks pretty simple... much easier than the standard APIs i use for various k8s automations