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

Hi folks- I’m trying to instantiate &amp; use a kubernetes config from another stack and having trouble getting the argument types right. Can anyone point me in the right direction? code and error message follows in thread.

Code: ```let kubeConfig = new pulumi.StackReference("mikedougherty/megadoomer-core/main").getOutput("kubeconfig");
let kubernetes = new k8s.Provider("k8s", { kubeconfig: kubeConfig} );

const vpn = new k8s.helm.v2.Chart("openvpn", {
    repo: "stable",
    chart: "openvpn",
    values: {
        "openvpn.OVPN_K8S_POD_NETWORK": "10.1.0.0",
        "openvpn.OVPN_K8S_POD_SUBNET": "255.255.0.0",
        "openvpn.OVPN_NETWORK": "10.1.240.0",
        "openvpn.OVPN_SUBNET": "255.255.255.0",
        "openvpn.redirectGateway": false,
    },
}, { providers: [kubernetes] });
``` and i’ve tried a few other variations for the `{providers: ...}` map in the final argument as well.

Error message from preview portion of `pulumi up`: ```error: pulumi:providers:kubernetes resource 'k8s's property 'kubeconfig' value {map[...]} has a problem: provider property values must be strings``` (map contents redacted / removed for brevity)

you try making it a string?

```
let kubernetes = new k8s.Provider("k8s", { kubeconfig: JSON.stringify(kubeConfig)} );
```

The kubeconfig property wants the YAML version of the config - in AKS (for example) that is exposed via `kubeConfigRaw`(in typescript). I’m not 100% certain about how it’s exposed by others - but that’s the issue here.

<@UD2HJDBCL> your solution worked with a slight tweak: ```let kubernetes = new k8s.Provider("k8s", { kubeconfig: kubeConfig.apply(JSON.stringify) } );```. thanks! i thought that the problem was in the `new Chart` but I guess was looking in the wrong place. thanks very much!

<@UB8A66MPS> thanks, i might check in on switching to AKS at some point and will keep that in mind