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

Yep, you can use the `.get` method
<https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/kubernetes/core/v1/#Secret-get>

Unrelated: the doc says that `default` namespace would be used by default “per Kubernetes convention”.  Wouldn’t the convention be to use the namespace associated with the ~ambiant~ provider kubecontext?

Hmm, you’re probably right. I assume you mean if the kubeconfig `context` has a different namespace set?

If that’s the actual behavior, it is good and it is a simple doc error.  If `default` is blessed, that would seem like a mistake in my mind.

I’m not sure if we handle that in the provider. Let me check

Nope, it looks like it’s ignoring the current-context namespace

<https://github.com/pulumi/pulumi-kubernetes/issues/971>