How to get notified when new EKS platform versions are available?

Question

EKS does not allow us to specify the k8s patch version when creating a cluster. It would be great to know when a new k8s version is available (especially regarding patch version).

We have some workload (portworx) that pulls kube-scheduler and kube-controller-manager based off of the kubernetes version (based off eks platform version), however it must come from our private ecr repos. Due to various business restrictions, we cannot use a pull-through cache. I would like to set up an automation so that when a new EKS version is available, it will clone the official images to our private repo (along with update some configurations in Git). We create and destroy cluster on a frequent basis, so we are currently running into ImagePullBackoff issues when a newly created EKS cluster is on a higher patch version than what our ecr repos have available.

Ideally we would have a push-based event-driven workflow, not pull-based.

Any help would be great! :)

re:Post Agent · Answer

While Amazon EKS doesn't provide a direct push-based notification system for new Kubernetes versions, there are several approaches you can consider to stay informed and automate your workflow:

1. Review the EKS Kubernetes release calendar: Amazon EKS typically releases three minor versions of Kubernetes annually, with each minor version supported for about 14 months. Regularly checking this calendar can help you anticipate upcoming releases.

2. Use AWS Health Dashboard: Although not specifically for EKS version updates, the AWS Health Dashboard can provide notifications about various AWS services, including EKS. You might receive notifications about new EKS versions through this channel.

3. Set up an AWS Lambda function: You could create a Lambda function that periodically checks the EKS API for available versions and compares them with your current versions. If a new version is detected, the function could trigger your automation workflow.

4. Utilize AWS EventBridge: While not directly tied to EKS version releases, you could set up an EventBridge rule that triggers on a schedule to check for new EKS versions. This could then initiate your automation process.

5. Monitor the official EKS GitHub repository: Amazon often announces new EKS versions on their GitHub repository. You could set up a GitHub webhook to notify you of new releases.

For your specific use case of maintaining private ECR repos with up-to-date images, you could combine one of these notification methods with an automated pipeline that:

1. Detects a new EKS version
2. Pulls the official kube-scheduler and kube-controller-manager images
3. Pushes these images to your private ECR repos
4. Updates your Git configurations

This approach would allow you to maintain your private repos with the latest images, avoiding ImagePullBackoff issues when creating new clusters.

Remember, while these methods can help you stay informed about new EKS versions, it's crucial to review the release notes and test thoroughly before upgrading your production clusters.  
**Sources**  
[Best Practices for Cluster Upgrades - Amazon EKS](https://docs.aws.amazon.com/eks/latest/best-practices/cluster-upgrades.html)  
[Prepare for Kubernetes version upgrades with cluster insights - Amazon EKS](https://docs.aws.amazon.com/eks/latest/userguide/cluster-insights.html)

How to get notified when new EKS platform versions are available?

Relevant content