This message was deleted.

That’s the way apiVersions work with Kubernetes. The resource was created with the apiVersion you specified, and then the k8s server will store that configuration in a common representation server-side. At that point, you can request that resource using any supported apiVersion, and it will auto-convert the stored configuration to the appropriate version for your request. You can see this behavior with

kubectl

by creating a Deployment and then trying both

kubectl get deployments.extensions -o yaml

and

kubectl get deployments.apps -o yaml

Pulumi will use the latest available apiVersion when it queries resource state.

But in my case I wanted to use the latest version of autoscaling/v2beta2, which is installed on our EKS. and also specifically requested that version.. but I got v1 deployed..

Are you seeing an error somewhere? Perhaps I don’t understand your question.