Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version option for update cluster command #909

Closed
arun-gupta opened this issue Jun 19, 2019 · 4 comments
Closed

Version option for update cluster command #909

arun-gupta opened this issue Jun 19, 2019 · 4 comments
Labels
area/upgrades kind/feature New feature or request priority/important-longterm Important over the long term, but may not be currently staffed and/or may require multiple releases

Comments

@arun-gupta
Copy link

eksctl update cluster does not allow to specify a version to upgrade to:

eksctl update cluster --help
Update cluster

Usage: eksctl update cluster [flags]

General flags:
  -n, --name string          EKS cluster name
  -r, --region string        AWS region
  -f, --config-file string   load configuration from a file
      --approve              Apply the changes
  -w, --wait                 wait for all update operations to complete before exiting (default true)

How does eksctl know which version to upgrade to?

@arun-gupta arun-gupta added the kind/feature New feature or request label Jun 19, 2019
@errordeveloper
Copy link
Contributor

@arun-gupta this was covered by initial discussion, but we didn't have an issue for it - thanks for opening it. The challenge her is that you can only go up by one version at a time, we will need to decide if we should automatically chain X number of upgrades, which will make the logic a little more complex.

@arun-gupta
Copy link
Author

Agreed, that per skew policy, control plane can be upgraded only one minor version. But chaining X upgrades would be a simplified experience. Particularly, if #906 makes the update a holistic experience.

@scottyhq
Copy link

It would be great to also clarify how patch versions are dealt with (for example how to upgrade from 1.13.7 to 1.13.8). https://docs.aws.amazon.com/eks/latest/userguide/platform-versions.html

eksctl get cluster simply shows 1.13.

But Sometimes situations come up where it is desirable to apply patched versions to the cluster and nodegroups: aws/amazon-vpc-cni-k8s#282 (comment)

@martina-if martina-if added the priority/important-longterm Important over the long term, but may not be currently staffed and/or may require multiple releases label Sep 9, 2020
@aclevername
Copy link
Contributor

Closed by #2318

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/upgrades kind/feature New feature or request priority/important-longterm Important over the long term, but may not be currently staffed and/or may require multiple releases
Projects
None yet
Development

No branches or pull requests

5 participants