Ninja Docs Help

Update AWS EKS cluster

Revision

Date

Description

1.0

24.07.2024

Init Changelog

This article explains how to update AWS EKS cluster with its components.

Requirements

  • Access to AWS EKS management console (edit permissions).

  • (optional) Terraform installed and access to IaC code.

Instructions

To perform AWS EKS cluster upgrade you need to:

  1. Login to AWS Console.

  2. Search for AWS EKS Console and open it.

  3. Go to Clusters view and find your cluster to update.

  4. Click Update now next to current cluster version under Kubernetes version tab.

  5. From dropbox select next Kubernetes version (you can only run update for one version at time).

  6. Click Update and wait till cluster’s status change Updating → Active (you can refresh page or console to check current status).

  7. Go into cluster details (click on it’s name on list).

  8. Go into Compute tab.

  9. Perform Node Rolling Update by selecting Update now next to AMI release version for all Node groups with settings (you can run Update for all Node Groups at once - AWS will create new Nodes and after that will perform termination of old Nodes):

    Aws eks update cluster 1
  10. Wait till Node Groups update ends (each Node Group Status will be Active) - if it takes too long (more than 30min), take a look on old nodes workload. It may be stuck. Check status or logs and decide you will wait or kill stuck pods.

  11. Go to Add-ons tab.

  12. Choose Update version (do it for every add-on!) and set it up:

    1. Version: Latest

    2. Select IAM role: Inherit from node

    3. Optional configuration settings → Conflict resolution method: Preserve

  13. Wait till every add-on will be in Status Active.

  14. (optional) Clone Terraform code repository with cluster definition on your workstation and checkout on pro

  15. (optional) Edit eks module:

    1. set new Kubernetes version in cluster_version.

    2. for every aws_eks_addon update addon_version (check add-on names!).

  16. (optional) Run terraform plan on project and check if there are no version changes.

  17. Commit and push changes to remote repository.

Last modified: 17 February 2025