Currently spread exits after it creates the localkube container. However, depending on if the weave images have been pulled or not it can be a long wait until the API server comes up. This can be confusing to users as the localkube container is running but not started. Experienced users have checked logs but we should provide a better way to communicate the setup state to the user.
It would be nice if status messages were displayed until the API server came up. It could error after a reasonable timeout (5 min?). This functionality should be able to be disabled with a parameter which would simply start the container.
Currently spread exits after it creates the localkube container. However, depending on if the weave images have been pulled or not it can be a long wait until the API server comes up. This can be confusing to users as the localkube container is running but not started. Experienced users have checked logs but we should provide a better way to communicate the setup state to the user.
It would be nice if status messages were displayed until the API server came up. It could error after a reasonable timeout (5 min?). This functionality should be able to be disabled with a parameter which would simply start the container.