https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rancher-desktop
a
This message was deleted.
f
Can you show the output? I think 
kuberlr
will not change versions if the current version is compatible according to the Version Skew Policy | Kubernetes 
kubectl
is supported within one minor version (older or newer) of 
kube-apiserver
.
From flavio/kuberlr: A tool that simplifies the management of multiple versions of kubectl > kuberlr reuses an already existing binary if it respects the kubectl version skew policy, otherwise it downloads the right one
m
You are right. Thank you
I ended up making some checks with the cluster and pull the new version and then it updates
f
You can always 
rm -rf ~/.kuberlr
to delete your cache if you want to force it to download an exact match
Which should rarely be necessary. Only case I can think of is when you need a newer feature in 
kubectl
that is not supported by the older version.
m
I ended up doing the following in a readiness check:
Copy code
aws eks describe-cluster --name dev | jq -r .cluster.version
I take that version then:
Copy code
kuberlr get "$cluster_version"
cluster_version_full="$(kubectl version -o json 2>/dev/null | jq -r .serverVersion.gitVersion | sed 's/v\([0-9]*\.[0-9]*\.[0-9]*\).*/\1/')"
kuberlr get "$cluster_version_full"
f
I guess that works, but there should be a simpler/builtin way in 
kuberlr
to do that (see the issue I linked above). But somebody has to implement it; discussing it on GitHub doesn't magically make it happen… 😄
m
It would really be nice to have it working out of the box but you are right, it will require the work to be done.
5 Views
Open in Slack
PreviousNext
Powered by