Hello again! Today when I was trying to setup multi-stack configuration with exporting kubeconfig to another stack I found a strange issue with assembling kubeconfig yaml used as an export. This example shows how to create that kubeconfig: https://github.com/pulumi/examples/blob/master/gcp-ts-gke/cluster.ts#L27-L56. What I tried is to replace this part of the code:

export const k8sConfig = pulumi.
    all([ k8sCluster.name, k8sCluster.endpoint, k8sCluster.masterAuth ]).
    apply(([ name, endpoint, auth ]) => {
        const context = `${gcp.config.project}_${gcp.config.zone}_${name}`;
        return `apiVersion: v1...

with:

export const k8sConfig = pulumi.
    all([ k8sCluster.project, k8sCluster.region, k8sCluster.zone, k8sCluster.name, k8sCluster.endpoint, k8sCluster.masterAuth ]).
    apply(([ project, region, zone, name, endpoint, auth ]) => {
        const location = region || zone
        const context = `${project}_${location}_${name}`
        return `apiVersion: v1...

If you are seeing

[object Object]

it typically means you are attempting to toString an

Output

. Instead, you need to use

output.apply(x => x.toString())

or similar. For example to log the Output you would want to do

output.apply(console.log)

. The value of these `Output`s is not known unti the deployment has happened, which is why these are wrapped inside

Output

instead of just string values. The

pulumi.all

and

pulumi.apply

above are part of taking all of these Outputs and using them to construct a new string value for the kubeconfig.

I am actually using pulumi.all 🙂