You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you get an error, you can easily retry, but if it's not working, and you want to start from scratch, it's not possible anymore to just refresh the browser as we persist the session: the installation will just restart as if you press the retry button. You can play with the session storage, but it's not as user-friendly.
This button should probably be available even if the installation did not fail in case kubefirst does not report any error, and the process just continue, but nothing is happening.
Most users do launch down and up again to mimic a reset button, but it's a bit more complicated for folks using Helm to install cluster 0 on an existing Kubernetes cluster.
Is this missing feature preventing you from using kubefirst?
Yes
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Even for users using launch up and down this would be faster. My cloud token isn't valid anymore, so I need to change it before using the retry button, so my only way right now is to launch down, and start over.
What is your feature idea?
Add a reset button to the console installation UI
Why is it needed?
If you get an error, you can easily retry, but if it's not working, and you want to start from scratch, it's not possible anymore to just refresh the browser as we persist the session: the installation will just restart as if you press the retry button. You can play with the session storage, but it's not as user-friendly.
This button should probably be available even if the installation did not fail in case kubefirst does not report any error, and the process just continue, but nothing is happening.
Most users do
launch down
andup
again to mimic a reset button, but it's a bit more complicated for folks using Helm to install cluster 0 on an existing Kubernetes cluster.Is this missing feature preventing you from using kubefirst?
Code of Conduct
The text was updated successfully, but these errors were encountered: