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

<@UFM2CJXA5> I don’t think I understand this, actually

Me either honestly haha. This happens with the new pulumi kubernetes 1.2

I mean, what code did you write that causes this

in the code for HPA, it is clear that those aliases aren’t in the alias list

so they must be coming from outside. your code? somewhere else?

I just boarded a plane unfortunately. I am not using the alias functionality at all in my code. It seems to be a bug in the new auto API version aliasing

The resource it happens on is just chance based on whatever is last or something

Not necessarily the HPA if I get rid of something else. TS

I don’t see where we could be introducing those aliases. no code you can share until you land, I guess?

I probably can share in a bit on the flight. Flying to Japan lol

if I can reproduce the issue I can fix it really quick

It's basically just a mixed bag of k8s resources though.

yeah, I just mean, if I have the code I can run it and sett the problem, which usually means i can debug in ~15 minute

I can’t tell for sure what the problem is from the info you provided, but my best guess would be that you have two `traffic-mirror` Deployments in the stack that have different apiVersions. This change effectively means that the apiVersion isn’t part of the URN anymore, so it would cause a conflict in that case.

Sorry travel got a bit crazy, this is the code: <https://gist.github.com/timmyers/7ffbb5856c8337725bff43626e2f0ab2>