^ does it use the new `apiVersion`s for ingress deployment

Question

cool-egg-852 · Answer

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

cool-egg-852 · Answer

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

cool-egg-852 · Answer

I know there was an open issue about it

gorgeous-egg-16927 · Answer

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

gorgeous-egg-16927 · Answer

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

gorgeous-egg-16927 · Answer

^ This is for a 1 16 cluster You ll get a deprecation warning rather than an error for previous versions

bitter-dentist-28132 · Answer

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

gorgeous-egg-16927 · Answer

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

bitter-dentist-28132 · Answer

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

bitter-dentist-28132 · Answer

i m on a v1 15 cluster fwiw

cool-egg-852 · Answer

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

cool-egg-852 · Answer

It s warning you that with 1 16 and newer your stuff will break

bitter-dentist-28132 · Answer

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

cool-egg-852 · Answer

Yes exactly

cool-egg-852 · Answer

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