https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
w
Copy code
const cluster = new eks.Cluster("my-cluster", {
    version: "1.14",
});
Worked for me
c
This is an existing node group which was already spun up with 
1.13
and now trying to upgrade to 
1.13.10
w
Yeah I upgraded from 1.13 to 1.14
All I changed was that version in 
ClusterOptions
IIRC
Looks like either version should work
Have you tried to find the ami in the aws console?
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.
c
Looks like https://docs.aws.amazon.com/eks/latest/userguide/eks-optimized-ami.html I would have to use 
amiid
from this.
Going to try that. Thank you.
w
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.
c
yes, that’s what I was hoping for.
w
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
Open in Slack
PreviousNext
Powered by

Pulumi Community

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.

Powered by