As a developer/user I would like to ensure that I'm using the latest version of clusterctl so that I don't run into unintended side effects.
Detailed Description
For example, when providers started using envsubst style vars (${var:=default}) in their templates, older versions of clusterctl would error out since it couldn't process these variables.
It would be nice to have something like the github cli where it checks if there are newer versions available.
$ gh
Work seamlessly with GitHub from the command line.
...<snip>...
A new release of gh is available: 0.10.0 → v0.10.1
https://github.com/cli/cli/releases/tag/v0.10.1
This solution would work since clusterctl is being shipped as part of CAPI releases.
The output below is from a released version of clusterctl (v0.3.8)
As extra credit, if clusterctl has a development version (v0.3.8 vs v0.3.8-24-76a9f1a2ce37cd), it can let the user know if there are newer commits to CAPI main branch.
This would mitigate recent issues regarding the CAPV pre-release. That is, clusterctl was updated with metadata for CAPV but older versions of clusterctl didn't know about it. However, this would cater specifically to the developer persona.
User Story
As a developer/user I would like to ensure that I'm using the latest version of clusterctl so that I don't run into unintended side effects.
Detailed Description
For example, when providers started using envsubst style vars (
${var:=default}
) in their templates, older versions of clusterctl would error out since it couldn't process these variables.It would be nice to have something like the github cli where it checks if there are newer versions available.
This solution would work since
clusterctl
is being shipped as part of CAPI releases. The output below is from a released version ofclusterctl
(v0.3.8)Anything else you would like to add:
As extra credit, if clusterctl has a development version (
v0.3.8
vsv0.3.8-24-76a9f1a2ce37cd
), it can let the user know if there are newer commits to CAPI main branch.This would mitigate recent issues regarding the CAPV pre-release. That is, clusterctl was updated with metadata for CAPV but older versions of clusterctl didn't know about it. However, this would cater specifically to the developer persona.
/kind feature /area clusterctl