Closed sherl0cks closed 5 years ago
~/.kube/config looks identical (apart from tokens) regardless of whether oc
or odo
creates it
Bummer - was getting ready to build a demo with odo
. looks like I need to do it with oc
. I updated my oc
to latest version (matching server) and nothing. Is there state outside of ~/.kube that I can clear?
Can you test this one (and the other issue) with latest binary from master (https://dl.bintray.com/odo/odo/latest/)
Looks like the issues are resolved. It was not the new client (as I did see some issues) right after switching. Perhaps some weird transient issues. I also test with minishift and things are back to normal. Sorry for noise.
[kind/bug]
What versions of software are you using?
odo version
:odo v0.0.17 (HEAD)
How did you run odo exactly?
see logs
Actual behavior
odo
cannot connect to cluster. seems it is truncatinghttps://
from the server urlExpected behavior
odo can talk to the server...
Any logs, error output, etc?
odo
oc