-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
🌱 upgrade clusterctl used for e2e test upgrade tests to v0.3.22 #4995
🌱 upgrade clusterctl used for e2e test upgrade tests to v0.3.22 #4995
Conversation
Signed-off-by: Stefan Büringer [email protected]
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Soon or later we have to find a way to automate this...
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fabriziopandini The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Conceptually we could also just specify something like "latest v0.3.x" and then our code searches on Github what the latest release/binary is? (Afaik similar to what clusterctl does right now with the YAMLs) |
/cc @fabriziopandini |
Yes, that's the idea... |
Yeah that could be interesting for all kinds of CAPI consumers like it is in the case of Kubernetes (although they have a few more consumers :)) |
Let's open an issue... |
@fabriziopandini I put it on my list, probably tomorrow. |
Signed-off-by: Stefan Büringer [email protected]
What this PR does / why we need it:
This PR updates the clusterctl version we use for our clusterctl upgrade e2e test. I assume we want to use more or less the latest version.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #