This message was deleted.
# generala
adamant-kite-43734
02/27/2026, 12:12 PMThis message was deleted.
c
creamy-pencil-82913
02/27/2026, 8:19 PMkube-proxy is generally built into the Kubernetes cluster distribution, not deployed or managed by Rancher. So that is something you’d need to work on the EKS side.
e
early-lion-52243
03/01/2026, 5:18 PMThank you
early-lion-52243
03/02/2026, 12:03 PM@creamy-pencil-82913 Interesting addition to this. When the cluster is created, it deploys the EKS kube-proxy correctly but to manage the version of this, I needed to add the kube-proxy add-on in AWS EKS console to control the versions deployed to it. Is this a bug or standard process?
c
creamy-pencil-82913
03/02/2026, 5:29 PMIt's not Rancher doing the deploying of kube-proxy. This is all eks, as far as I know.
c
careful-pager-2164
03/02/2026, 6:06 PMaws dashboard - eks - select your eks cluster -> add-ons tab is what your probably looking for
e
early-lion-52243
03/03/2026, 8:10 AM@careful-pager-2164 Yes that's where I added the kube-proxy addon. Just interesting that it needs to be added as an extra even though it's been deployed during provisioning and to manage the version of this it needs to be done through the addons
c
careful-pager-2164
03/03/2026, 4:51 PMhey, aws = another weed/weird service/solution ......
careful-pager-2164
03/03/2026, 4:52 PMits like the 30 teams building 1 service all have their own thing - they cant even decide on a central confirm delete message on the platform
😆 1
45 Views