Containers-roadmap: [EKS]: One-click Full Cluster Upgrade

[mohitanchlia]

Automation in EKS as a service has come in only bits and pieces. EKS with managed nodes is not really that useful without having a one click full upgrade where EKS version, aws-node, dns etc. along with the worker nodes get upgraded without running or orchestrating commands manually. This can be broken down into 2 pieces 1) Full cluster upgrade with nodes 2) Only worker node upgrades for ongoing AMI rotation. This is a critical functionality

[tabern]

Renaming this to 'One-click Full Cluster Upgrade'. Today EKS managed nodes supports worker node upgrades for AMI rotation, but this is not yet in the console (https://github.com/aws/containers-roadmap/issues/605). See API documentation here: https://docs.aws.amazon.com/eks/latest/APIReference/API_UpdateNodegroupVersion.html

[mtparet]

I just read the official documentation of AWS to upgrade an eks cluster : we have to manually execute kubectl commands to upgrade critical components of Kubernetes.
Really, for a "managed" service, is it a joke ?
Even updating my on-premise cluster is easier than updating the called "managed" AWS Kubernetes service.

https://docs.aws.amazon.com/eks/latest/userguide/update-cluster.html

[irperez]

In Azure AKS, this is a single click operation with a version drop down.

[sandrom]

The upgrade process cant get enough love, please work on this! It is incredibly important for production workloads to have a managed process for this :)

[raravena80]

+1 for this

[ghost]

+1
EKS need to close the gaps with AKS and GKE

[nydalal]

+1

[damscott]

This feature could impact people working under the assumption that AWS will not modify resources running inside the cluster, notably kube-proxy (#657)

[kylecompassion]

+1