EKS depreciation k8s 1.15 , eks-jx upgrade ?

[thpham]

Summary

Hello,

2 weeks ago, I got an AWS notice that EKS 1.15 will be deprecated and that we should move on to 1.16 asap or that the cluster will be updated automatically on May 3, 2021.

I created my cluster at the time with the version v1.1.0 and fixed this eks-jx module to a private fork, like the current recommendation for production cluster consideration.

What is the recommended way now to upgrade ?

options:

1. wait for the automatic upgrade from AWS EKS

2. force the upgrade by updating the terraform variable of this module that specify the new supported cluster version (1.16)
   -> I did a terraform plan to see what changed and I see 4 to add, 3 to change, 2 to destroy , which looks a bit scary ...

Thank you for your advices.

Module version

module v1.1.0

Operating system

eks 1.15

[thpham]

FYI: there was a discussion, on slack https://kubernetes.slack.com/archives/C9MBGQJRH/p1618305305033100
suggestion is to move directly on 1.17 ...