-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to use nodeshift in Katacoda environments #197
Labels
Comments
lholmquist
added a commit
to lholmquist/nodeshift
that referenced
this issue
Mar 12, 2018
…ift-config-loader. * This was previously taken out, but is needed again. * use --configLocation on the cli or the options.configLocation in the API fixes nodeshift#197
lholmquist
added a commit
to lholmquist/nodeshift
that referenced
this issue
Mar 12, 2018
…ift-config-loader. * This was previously taken out, but is needed again. * use --configLocation on the cli or the options.configLocation in the API fixes nodeshift#197
ghost
assigned lholmquist
Mar 12, 2018
ghost
removed
the
review
label
Mar 12, 2018
Wahoo!! Once this shows up in a npm-consumable release I'll be sure to remove my workarounds (which right now is a symlink added to |
@jamesfalkner i just published it to npm, as 1.5.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I went to upgrade to latest nodeshift in a project that runs in a Katacoda environment, where the configuration file for the oc command is not at
~/.kube/config
. It's actually at/openshift.local.config/master/admin.kubeconfig
, and I was using the configLocation in nodeshift to point at it. I'm not an expert at kubernetes config locations and don't know if this is a bad practice, but removing this from nodeshift prevents my project from using latest nodeshift as this environment does not place the kube config file in the place that nodeshift now requires.The text was updated successfully, but these errors were encountered: