killed kiosk process. run new kiosk but helm errors out. about kiosk-console HOT 6 CLOSED

I think this is probably expected behavior, since the new kiosk does not have access to the keypair that was used for communication with the old cluster. @osterman can you comment on this?

Also, could this be related to #24 ?

from kiosk-console.

The connection to the server localhost:8080 was refused

See: https://docs.cloudposse.com/faq/running-kubectl-fails-connection-refused/

from kiosk-console.

@willgraf, can you recreate this error and see if the fix linked to by @osterman takes care of it? If so, I can make a branch where dropping to the shell before creating a cluster within a kiosk (implying that you want to interface with a pre-existing cluster) leads to the user being prompted to enter the name of the cluster they want to interact with and then that input is used to implement @osterman's fix.

from kiosk-console.

Also, @willgraf, did you go through the configuration process for whichever cloud you were using before dropping to the shell in your second kiosk? If not, is that sufficient to fix this? If so, then maybe it makes sense to just document this in the troubleshooting doc?

from kiosk-console.

@osterman I ran the command mentioned in the help page you linked to, but got an error that export was not a kubectl command.

from kiosk-console.

I'm going to close this as stale, since it has not been encountered in over a year.

from kiosk-console.