kubectl CLI is outdated by several versions about arkade

[rgee0]

I've proposed a change covering the maintenance side of this

[James5979]

arkade version output:

...
Version: 0.11.6
Git Commit: acb1bd9
...

Apologies if you received any email noise from this issue, I accidentally submitted before I had finished writing.

[alexellis]

Hi @James5979 are you happy to send a PR to update to the latest version?

We can look separately at the version lookup later.

[James5979]

Hi @James5979 are you happy to send a PR to update to the latest version?

Hi @alexellis,

Thank you for your quick reply.

I would create a PR, but unfortunately I do not know Go.

If you remember this being something trivial to update then I can always have a look for you.

We can look separately at the version lookup later.

Nothing major, just a suggestion for the future.

As a workaround, I can always track stable with:

arkade get kubectl@$(curl -L -s https://dl.k8s.io/release/stable.txt)

A bit out of context, but I purchased one of your inlets pro personal licenses the other day and it is amazing! I have been using the inlets operator and I will definitely update you on how it works out. 🙂

[alexellis]

I also updated kubectl without seeing Richard's PR.

We wanted to add a set of resolvers for versions, with the default being GitHub, then adding K8s and Hashicorp (if possible).

The Go templates won't contain a function, but would reference i.e. "resolver" as part of their definition to be used at runtime.

Would either of you like to have a go at breaking out one for GitHub releases and a separate one for the K8s stable.txt file?