You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 23, 2024. It is now read-only.
get-cli downloads kubectl and dcos to the working directory. It never checks if the binaries are already available, if the version matches, etc. before downloading, so every call downloads the binaries to the working directory.
setup-cli calls dcos from the working directory. It doesn't check if the binary is available, if the version matches, etc.
Then, references to kubectl always assume that kubectl is available in $PATH. If that's the case, we may end up with a kubectl v1.7.x in $PATH being called to interact with Kubernetes 1.10.3, even after get-cli downloaded kubectl v1.10.3 to the working directory.
I ran into this just now and it was painful to figure out.
My suggestion is to keep thing simple and just check for dcos and kubectl in $PATH, and show a warning about potential conflicts if their versions don't match the server-side versions.
The text was updated successfully, but these errors were encountered:
get-cli
downloadskubectl
anddcos
to the working directory. It never checks if the binaries are already available, if the version matches, etc. before downloading, so every call downloads the binaries to the working directory.setup-cli
callsdcos
from the working directory. It doesn't check if the binary is available, if the version matches, etc.Then, references to
kubectl
always assume thatkubectl
is available in$PATH
. If that's the case, we may end up with akubectl
v1.7.x in$PATH
being called to interact with Kubernetes 1.10.3, even afterget-cli
downloadedkubectl
v1.10.3 to the working directory.I ran into this just now and it was painful to figure out.
My suggestion is to keep thing simple and just check for
dcos
andkubectl
in$PATH
, and show a warning about potential conflicts if their versions don't match the server-side versions.The text was updated successfully, but these errors were encountered: