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

Unless I’m misunderstanding your question, that’s on you to make the change to.

Pulumi has supported it for as long as I can remember. If you are asking about the auto aliasing, I don’t recall a PR being merged in for that request yet.

Right, the SDK will continue to support any apiVersion of the k8s resources. It’s up to the user to use a supported version depending on the cluster they’re targeting

image.png

I’ve been improving related error messages as well, so it should be clear if you are using a deprecated or removed apiVersion and how to fix.

^ This is for a 1.16 cluster. You’ll get a deprecation warning rather than an error for previous versions.

so I guess to the default for e.g. `k8s.apps.v1.Deployment` is the deprecated `apiVersion`?

I’m not sure I understand the question. The SDK includes `k8s.apps.v1.Deployment` as well as older versions like `k8s.extensions.v1beta1.Deployment`. Only the older versions cause the deprecation warnings

that's odd... i'm seeing the deprecation message for `k8s.apps.v1.Deployment`

Right, and you will. It will just be a warning not an error.

It’s warning you that with 1.16 and newer, your stuff will break.

ohhhh wait, it's saying that for the mongo chart, not my actual deployments. that's my bad, the mongo chart must be using the deprecated one.

I get the same thing for some helm charts too like cert-manager