If users use up space init to conveniently bootstrap a Space and forget to set the account string, the spaces-controller pod never becomes healthy and goes into a crashloopbackoff.
It would be good to alert users to the issue before attempting to do the install.
What happened?
If users use
up space init
to conveniently bootstrap a Space and forget to set the account string, the spaces-controller pod never becomes healthy and goes into a crashloopbackoff.It would be good to alert users to the issue before attempting to do the install.
What environment did it happen in?
Spaces v1.3.0 with up v0.28.0