Not strictly enforce K8s auto-upgrades for out-of-support versions except for security reasons

Even though Azure and GCP support three GA minor versions of Kubernetes, they do not enforce auto-upgrades for out-of-support versions. ISV's end customers face challenges to stay up-to-date with all releases and when EKS is auto-upgraded to a version that is not compatible with ISV product, then the related customer workloads will break until everything is upgraded. Delaying auto-upgrade will provide some window for ISV customers that are not used to rapid deployments.

No files, tests, or entry points are mentioned. Start by reviewing the EKS auto-upgrade behavior described in the issue and define how out-of-support versions should be handled, including the security exception; done means the requested upgrade policy is agreed and documented.

Written by the indexing model from the issue text.