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

Decided that filing an issue was probably better: <https://github.com/pulumi/pulumi-kubernetes/issues/2817>

Could you be destroying the namespace before the helm chart?

That is indeed possible since there’s no explicit dependency between the two. However, the pulumi stack state does still show the namespace being present.

Still running the issue, so doesn’t look like it’s a case of the namespace getting deleted before the release

You can use the dependsOn option to explicitly model the dependency

Or when you declare the helm Release, use the namespace output (metadata.namespace) as an input to the Release with the same effect

That’s what I’m doing now but still running into the same problem