Relationship between the EKS modules and Kubernetes version?
_This message was extracted from a discussion that originally took place in Gruntwork Community Slack. Names and URLs have been removed where appropriate_ **From a customer** Is there any sort of compatibility relationship between the gruntworks EKS modules and the Kubernetes version? If so, is there a matrix somewhere that I can check versions? Main reason/inspiration being we are tied to TF 0.12 for the next however long, which caps us at version 0.30 of the EKS modules for now. But ideally, we'd like to use the newest version of k8s available/stable with those modules. A secondary question is kubergrunt and backwards-compatibility, how 'new' can we use of KG with how old of a module, is there a matrix for taht as well?
**From a grunt** You should actually be able to use terraform 0.12.31 with the modules in `terraform-aws-eks` up to the latest actually. I would suggest trying to bump through the versions until you hit an error in the `plan`. Make sure you read through the release notes for each backward incompatibility (each version bump of the `X` in `0.X.Y`). AFAIK, we haven’t introduced anything that requires newer terraform versions yet at the `terraform-aws-eks` level. With that said, to answer your question, the last version to have close ties to the kubernetes version was `0.27.0`. Starting that release, kubernetes version updates functionality was migrated to `kubergrunt`, so the module version isn’t related to what kubernetes version you can deploy - it was more a function of `kubergrunt` version. For the second question, the only backward incompatibilities we’ve introduced in `kubergrunt` so far has been related to the kubernetes version, which closely tracks what EKS supports (that is, when EKS drops a kubernetes version, support for that version is dropped from `kubergrunt`). So given that, you can actually use the latest version kubergrunt with any version of `terraform-aws-eks`