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.

Sign up for GitHub

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

Jump to bottom

upgrade plan command #499

Closed
7 tasks done
Tracked by #551
mitalipaygude opened this issue Oct 26, 2021 · 2 comments
Closed
7 tasks done
Tracked by #551

upgrade plan command #499

mitalipaygude opened this issue Oct 26, 2021 · 2 comments
Assignees
@mitalipaygude
Labels
kind/enhancement New feature or request

Comments

@mitalipaygude
Copy link
Member

mitalipaygude commented Oct 26, 2021 •
edited by g-gaston
Loading

What would you like to be added:
An eksctl anywhere upgrade plan command that can be used to identify possible targets for upgrades.

clusterctl upgrade plan reference:
https://cluster-api.sigs.k8s.io/clusterctl/commands/upgrade.html

Produces an output like this:

Checking cert-manager version...
Cert-Manager will be upgraded from "v1.5.0" to "v1.5.3"

Checking new release availability...

Management group: capi-system/cluster-api, latest release available for the v1beta1 API Version of Cluster API (contract):

NAME                    NAMESPACE                           TYPE                     CURRENT VERSION   NEXT VERSION
bootstrap-kubeadm       capi-kubeadm-bootstrap-system       BootstrapProvider        v0.4.0           v1.0.0
control-plane-kubeadm   capi-kubeadm-control-plane-system   ControlPlaneProvider     v0.4.0           v1.0.0
cluster-api             capi-system                         CoreProvider             v0.4.0           v1.0.0
infrastructure-docker   capd-system                         InfrastructureProvider   v0.4.0           v1.0.0


You can now apply the upgrade by executing the following command:

   clusterctl upgrade apply --contract v1beta1

Why is this needed:
This would help users visualize the versions they are upgrading from and new available versions. Running this command before running the actual upgrade command can help users make a decision on if they want to go through the upgrade, or just inform them about the versions changes.
@mitalipaygude mitalipaygude added the kind/enhancement New feature or request label Oct 26, 2021
@mitalipaygude mitalipaygude added this to the next+1 milestone Oct 26, 2021
@danbudris
Copy link
Member

would be interested in having a machine-parsable output to this, in JSON perhaps. This could be useful for eventual integration with tools like a Terraform provider

@jaxesn jaxesn modified the milestones: next+1, next Nov 8, 2021
@g-gaston g-gaston mentioned this issue Nov 8, 2021
Closed
7 tasks
@mitalipaygude
Copy link
Member Author

mitalipaygude commented Dec 1, 2021 •
edited
Loading

  • Skeleton for the upgrade plan command
  • Display EKSA components
  • Display Flux components
  • Display CAPI components
  • Add JSON output flag
  • New cobra command for plan #822

This was referenced Dec 4, 2021
Closed
Merged
Merged
This was referenced Dec 13, 2021
Merged
Closed
Merged
@jaxesn jaxesn modified the milestones: next, next+1 Jan 12, 2022
@chrisnegus chrisnegus mentioned this issue Jan 26, 2022
Merged
@jaxesn jaxesn removed this from the next milestone Feb 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mitalipaygude mitalipaygude

Labels
kind/enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@jaxesn @g-gaston @danbudris @mitalipaygude