This message was deleted.

sparse-intern-71089

01/29/2020, 9:37 PM

This message was deleted.

gorgeous-egg-16927

01/29/2020, 10:24 PM

Yep, you can use the

.get

method https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/kubernetes/core/v1/#Secret-get

👍 1

able-crayon-21563

01/29/2020, 10:27 PM

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?

gorgeous-egg-16927

01/29/2020, 10:30 PM

Hmm, you’re probably right. I assume you mean if the kubeconfig

context

has a different namespace set?

able-crayon-21563

01/29/2020, 10:30 PM

yes.

able-crayon-21563

01/29/2020, 10:31 PM

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.

gorgeous-egg-16927

01/29/2020, 10:31 PM

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

gorgeous-egg-16927

01/29/2020, 10:37 PM

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

gorgeous-egg-16927

01/29/2020, 10:37 PM

I’ll open an issue to track

able-crayon-21563

01/29/2020, 10:37 PM

Thanks for taking a look.

👍 1

gorgeous-egg-16927

01/29/2020, 10:46 PM

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

5 Views

Open in Slack

Previous Next

Pulumi Community

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.