Please mention/point to the aws-eks-ami release in the AMI list about amazon-eks-user-guide HOT 5 CLOSED

@ankon today we've added Kubernetes patch version numbers to the AMI lists. Hopefully this helps a bit with identifying when a new AMI ships (typically for new minor and patch version releases).

https://docs.aws.amazon.com/eks/latest/userguide/eks-optimized-ami.html

from amazon-eks-user-guide.

Thanks for that.

However, that still doesn't really change the process in finding what exactly has changed in the AMIs.

I thought a bit about what would help me, and basically it is really just a change in the wording so that the eks-optimized-ami.html not just mentions the produced AMI IDs, but also the name of the tag/changelog entry in the amazon-eks-ami changelog. I would then be able to take that value, and in my own documentation write down which version we deploy, and which AMI ID was used. I'm already watching for new releases in amazon-eks-ami.

from amazon-eks-user-guide.

Hi @ankon. The tags in the changelog correspond to the names of the AMIs. So you can describe any AMI that we have published publicly and get the name of the AMI, compare it to its name in the changelog, and then see the differences for that revision. Here is an AWS CLI command to describe today's recommended 1.13 worker node AMI:

aws ec2 describe-images --region us-west-2 --image-ids ami-089d3b6350c1769a6 --query Images[].Name
[
    "amazon-eks-node-1.13-v20190614"
]

So you could run this command on your current worker node AMI, and on the latest worker node AMI, and then you could infer which changelog entries separate the two. Does this workaround resolve your issue?

from amazon-eks-user-guide.

@nrdlngr that looks promising indeed, at least it makes the annoying "find the matching thing" step be quick and painless. Thanks!

from amazon-eks-user-guide.

Great! I'll close this issue then.

from amazon-eks-user-guide.