---
title: "Discussion on \"Stop Managing EKS Add-ons by Hand\" | Hashnode"
description: "Discussion on \"Stop Managing EKS Add-ons by Hand\". Originally published on graycloudarch.com.\n\nI was preparing to upgrade a production EKS cluster to version 1.32 when I discovered a problem.\nFour of our core cluster components—VPC CNI, CoreDNS, kube-proxy, and Metrics Server—were all running version..."
url: "https://hashnode.com/posts/stop-managing-eks-add-ons-by-hand-1/69d293967b9dd37d867911cc"
---

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

Discussion

# [Stop Managing EKS Add-ons by Hand](https://tallgray.hashnode.dev/stop-managing-eks-add-ons-by-hand-1?utm_source=hashnode&utm_medium=feed)

Originally published on graycloudarch.com. I was preparing to upgrade a production EKS cluster to version 1.32 when I discovered a problem. Four of our core cluster components—VPC CNI, CoreDNS, kube-proxy, and Metrics Server—were all running version...

Apr 5 · 5 min read · tallgray.hashnode.dev  
Read the article

-   [#eks](https://hashnode.com/tag/eks)
-   [#kubernetes](https://hashnode.com/tag/kubernetes)
-   [#terraform](https://hashnode.com/tag/terraform)
-   [#terragrunt](https://hashnode.com/tag/terragrunt)
-   [#infrastructure-as-code](https://hashnode.com/tag/infrastructure-as-code)

## Written by

[Glenn Gray](https://hashnode.com/@tallgray)

@tallgray · Denver, CO

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

Infrastructure Architect · AWS · Kubernetes · Terraform

I design multi-account AWS platforms, EKS/ECS clusters, and Terraform IaC that production teams can own and maintain. Writing about what I learn from real-world infrastructure work.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
