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

<@U01BRSYUUDP> where did this error come from? Pulumi?

yeah, found it. So i created the pull secret on my computer, when my kubeconfig was configured correctly for the both the cluster and the namespace. That worked. But in moving my code to a CustomResource, i forgot to add the k8s provider. So anytime i was not connected to the right cluster/namespace this would fail with the error above.

figured it out when i created a namespace and 10 difficult helm charts deployed without a hitch, and this stupid secret complained about the namespace not existing.

at some point i’ll stop asking stupid questions :slightly_smiling_face: