search

rancher / eks-operator

Apache License 2.0
22 stars 36 forks source link

Unable to upgrade nodegroup for an imported cluster after Rancher Upgrade from 2.8 to 2.9 #923

Closed valaparthvi closed 2 weeks ago

valaparthvi commented 2 weeks ago

Rancher Version: 2.8.9 or 2.8.5 Rancher Upgrade Version: 2.9-head EKS Operator Version: rancher/eks-operator:v1.9.4-rc.2

Steps to reproduce:

  1. Create a cluster on AWS via CLI eksctl.
  2. Import an EKS cluster to Rancher with k8s v1.28.
  3. Upgrade Rancher Version.
  4. Upgrade Control Plane version to k8s v1.29.
  5. Upgrade NodeGroup version to k8s 1.29

Results: NodeGroup version is not upgraded.

valaparthvi commented 2 weeks ago

Not a bug, but known issue. The cluster was created via CLI which uses custom launch template that can only be upgraded by updating launch template version.

You can't directly update a node group to a newer Kubernetes version if the node group was created from a custom launch template. You must create a new launch template with the proper Kubernetes version, and associate the node group with the new template. Ref: https://ranchermanager.docs.rancher.com/reference-guides/cluster-configuration/rancher-server-configuration/eks-cluster-configuration#user-provided-launch-templates