---
title: "Discussion on \"The EKS 1.32 1.33 Upgrade That Broke Everything (And How I Fixed It)\" | Hashnode"
description: "Discussion on \"The EKS 1.32 1.33 Upgrade That Broke Everything (And How I Fixed It)\". Introduction Upgrading Kubernetes should be boring.\nThis one wasn’t.\nI recently upgraded a production Amazon EKS cluster from 1.32 to 1.33, expecting a routine change. Instead, it triggered a cascading failure:\n\nNodes went NotReady\n\nAdd-ons stalled i..."
url: "https://hashnode.com/posts/the-eks-132-133-upgrade-that-broke-everything-and-how-i-fixed-it/694eb0783f0fc9e7279c249e"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [The EKS 1.32 1.33 Upgrade That Broke Everything (And How I Fixed It)](https://adedamolaajibola.hashnode.dev/the-eks-132-133-upgrade-that-broke-everything-and-how-i-fixed-it?utm_source=hashnode&utm_medium=feed)

Introduction Upgrading Kubernetes should be boring. This one wasn’t. I recently upgraded a production Amazon EKS cluster from 1.32 to 1.33, expecting a routine change. Instead, it triggered a cascading failure: Nodes went NotReady Add-ons stalled i...

Dec 26, 2025 · 4 min read · adedamolaajibola.hashnode.dev  
Read the article

-   [#kubernetes](https://hashnode.com/tag/kubernetes)
-   [#karpenter](https://hashnode.com/tag/karpenter)
-   [#devops](https://hashnode.com/tag/devops)
-   [#aws](https://hashnode.com/tag/aws)

## Written by

[Adedamola Ajibola](https://hashnode.com/@Adedamolaajibola)

@Adedamolaajibola · Lagos, Nigeria

  
[View profile](https://hashnode.com/@Adedamolaajibola)

DevOps tinkerer | Cloud enthusiast | Technical writer | Volunteering advocate

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
