Skip to content
This repository has been archived by the owner on Jan 4, 2022. It is now read-only.

Bail out if trying to start a cluster that was not created #325

Open
krnowak opened this issue Oct 24, 2018 · 1 comment
Open

Bail out if trying to start a cluster that was not created #325

krnowak opened this issue Oct 24, 2018 · 1 comment

Comments

@krnowak
Copy link
Member

krnowak commented Oct 24, 2018

Currently running kube-spawn destroy; kube-spawn start … will always result in a timeout when waiting for machines to be brought up. kube-spawn should rather fail much earlier, after noticing that the cluster was not created yet and telling to use kube-spawn create … first (or just use kube-spawn up …).

@dongsupark
Copy link
Member

+1. Yeah, it should be more friendly.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants