Amazon EKS Upgrade Journey From 1.23 to 1.24

We are now welcoming “Stargazer”. Process and considerations while upgrading EKS control-plane to version 1.24. <h1>Overview</h1> <img alt="" src="https://miro.medium.com/v2/resize:fit:700/0*izmIDPMa5uu28hUS.jpg" style="height:700px; width:700px" /> EKS finally announced support for Kubernetes version 1.24 . I am mega excited for everybody to experience the power of the “Stargazer” release. This time Kubernetes team selected “Stargazer” name for this release to honor the work done by hundreds of contributors across the globe: “Every single contributor is a star in our sky…” The long awaited feature of supporting only containerd runtime is finally here. You can no longer use dockerd runtime with your EKS 1.24 as worker node AMI doesn’t contain it. This is probably the most significant change in this release. Starting with version 1.24 of Kubernetes, the Amazon Machine Images (AMIs) provided by Amazon EKS will only support the containerd runtime. The <a href="https://github.com/awslabs/amazon-eks-ami/blob/master/files/bootstrap.sh" rel="noopener ugc nofollow" target="_blank">EKS optimized AMIs</a> for version 1.24 no longer support passing the flags <code>enable-docker-bridge</code>, <code>docker-config-json</code>, and <code>container-runtime</code>. <a href="https://marcincuber.medium.com/amazon-eks-upgrade-journey-from-1-23-to-1-24-b7b0b1afa5b4">Learn More</a>