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
Since we don't provide the kbot password with a CLI installation like we do in the UI, we should display the command to retrieve it easily in the Quick start section shown by the CLI after successful creation.
Why is it needed?
Since it's critical for using their new cluster, that some folks don't the documentation, we should make their life easier.
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:
Oh, you're right, it can be displayed with this command for the CLI installations, but there is nothing like in the UI that explain or tell you that you need to log with the kbot user only in kubefirst.
I would expect I could use the root token from Vault, but it let you connect to Vault, not be used for the SSO log in into kubefirst.
I think we could make the messaging clearer, WDYT?
What is your feature idea?
Since we don't provide the
kbot
password with a CLI installation like we do in the UI, we should display the command to retrieve it easily in the Quick start section shown by the CLI after successful creation.Why is it needed?
Since it's critical for using their new cluster, that some folks don't the documentation, we should make their life easier.
Is this missing feature preventing you from using kubefirst?
Code of Conduct
The text was updated successfully, but these errors were encountered: