Thomas Kappler

Hi @Rus1an31, sorry you're running into this. We'll be looking into it as soon as possible. In the meantime, would you be able to try again with a recent version...

Thanks for checking, @Rus1an31. Could you post the first few lines of the new stack trace to get accurate line numbers for debugging? It would also be very helpful if...

To narrow down the problem, I tested with a TypeScript program and it behaves the same. Turning on verbose logging, I see that the request to Azure is https://management.azure.com//providers/Microsoft.Authorization/roleDefinitions?%!f(MISSING)ilter=roleName+eq+%!i(MISSING)nvalid%!&(MISSING)api-version=2018-01-01-preview and...

Hi @imbelchev, thanks for raising this. It doesn't seem that it can be configured currently. I'm not a Functions expert. Would it be enough to change the version range to...

> @thomas11 , @mikhailshilkov , As the contribution was accepted and PR merged, do you have any timeline for when this change might get to an actual public release? @imbelchev...

Thank you for the suggestion, @infa-ddeore! I think this would be a good fit for pulumi-eks since it already covers [amazon-vpc-cni-k8s](https://github.com/aws/amazon-vpc-cni-k8s/). I think we'd need to for the underlying pulumi-aws...

@rquitales I think we also need to disable Fargate tests until this is resolved, otherwise we'll constantly get new P1s like this #1043.

Hi @pierskarsenbarg, reviewing the code I see that the missing version is supposed to come from one of two places: the `NodeGroupV2`'s arguments (optional), or else the cluster version. Is...

I see, @pierskarsenbarg. #855 looks like a plausible cause. Any luck specifying an explicit version as a workaround?

@pierskarsenbarg reading [the code](https://github.com/pulumi/pulumi-eks/blob/563970bf5d5ef8749f4e56007961fa49fa04ac4c/nodejs/eks/nodegroup.ts#L1144), it seems that it is the k8s version that's used in the AMI URL. Unless I'm misunderstanding something - I'm not super familiar with EKS. ```typescript...