Closed viddo closed 7 months ago
When triaging/working on this, be aware of the implications of this and the dynamic Kubetoken feature. If the CLI is not installed in the PATH, it won't be used for the Kubeconfig generated by Okteto.
This issue is stale because it has been open for 60 days with no activity. Comment on this issue or it will be closed in 7 days
Issue moved to JIRA: https://okteto.atlassian.net/browse/LAKE-110
FWIW, found workaround in case someone is interested in this for whatever reason, it's enough to make a shell script to get a hold of older versions by steps outlined in release → installation methods https://github.com/okteto/okteto/blob/eab2d4914fc3628455639bed71a0182cc8438477/docs/RELEASE.md?plain=1#L43-L62
Is your feature request related to a problem? Please describe. I'd like to install multiple versions of
okteto
and be able to choose where the binary is written. Primary use-case is for confirming bug before writing up a report, specifically to ease comparing behavior between a stable / beta version.Describe the solution you'd like
Hypothetical, proposed happy-path:
Describe alternatives you've considered
I'm aware that I can manually download a release from Github's release page, e.g. https://github.com/okteto/okteto/releases/tag/2.20.0-beta.1 but I find it clunky when there already exist a script
Additional context
OKTETO_INSTALLATION_PATH
is optionalOKTETO_INSTALLATION_PATH
requires a full path to binary if it's defined. E.g./tmp
would not be accepted and fail early