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

image.png

```
const cluster = new eks.Cluster("my-cluster", {
    version: "1.14",
});
```

This is an existing node group which was already spun up with `1.13` and now trying to upgrade to `1.13.10`

All I changed was that version in `ClusterOptions` IIRC

<https://github.com/pulumi/pulumi-eks/blob/master/nodejs/eks/nodegroup.ts#L383>

Have you tried to find the ami in the aws console?

<https://console.aws.amazon.com/ec2/home?region=us-east-1#Images:visibility=public-images;search=amazon-eks-node-;sort=desc:name>

You probably want `amazon-eks-node-1.13-v20190906`

i.e. there is no ami with `1.13.10` in the name

Never mind, it filters on the description, which does have the k8s version.

Looks like <https://docs.aws.amazon.com/eks/latest/userguide/eks-optimized-ami.html> I would have to use `amiid` from this.

Well, the code should find the ami id if you just specify the version. Not sure why it's not working for you.

According to the code, I'd expect you to just be able to specify version `1.13` and it would find the latest patch and apply it when you next update your stack; unless I'm missing something.

Ah, I think this is the "problem": <https://github.com/pulumi/pulumi-eks/blob/master/nodejs/eks/nodegroup.ts#L425-L426>

&gt; When we automatically pick an image to use, we want to ignore any changes to this later by default.

There's no way to opt in to upgrading discovered images, you have to specify the ami id at that point, which is unfortunate.

Another reason to prefer finding the ami by version is that it could / should find the ami in the same region as the stack

<https://github.com/pulumi/pulumi-eks/issues/88#issuecomment-530557544>