Hey fellas I just updated to ` pulumi kubernetes 2 7 8` and Pulumi Community #kubernetes

Hey fellas, I just updated to `@pulumi/kubernetes@...

prehistoric-account-60014

01/29/2021, 1:54 AM

Hey fellas, I just updated to

@pulumi/kubernetes@2.7.8

and I'm now getting errors due to a different format for secret data.

secret.data.apply(data => console.log(data))

is logging a wrapped object that looks something like this:

Copy code

{
  '4dabf18193072939515e22adb298388d': '1b47061264138c4ac30d75fd1eb44270',
  value: { privateKey: '<base64>' }
}

data

should just be

{ privateKey: '<base64' }

. Is this a bug or perhaps a breaking change? Has anybody else run into this issue?

prehistoric-account-60014

01/29/2021, 2:08 AM

I was using v2.6.2 before

billowy-army-68599

01/29/2021, 2:12 AM

cc @broad-dog-22463

prehistoric-account-60014

01/29/2021, 2:16 AM

What ended up happening was that the deployment pods stayed on

ContainerCreating

forever because I did

secret.data.apply(data => Object.keys(data)[])

to get the key for the mounted secret. But instead of

privateKey

I was getting

4dabf18193072939515e22adb298388d

, which Kubernetes couldn’t find and so it couldn’t mount the volumes and everything just hanged

prehistoric-account-60014

01/29/2021, 2:17 AM

For now I just hard-coded

'privateKey'

as a string, but it’s nice to be able to just use the output and keeping a single source of truth

sparse-park-68967

02/01/2021, 9:31 PM

what version CLI are/were you on?

prehistoric-account-60014

02/02/2021, 12:35 AM

v2.19.0

prehistoric-account-60014

02/02/2021, 12:36 AM

I think. I’m not 100% on that. I can try and set up a repro when I get some time

4 Views