-
Notifications
You must be signed in to change notification settings - Fork 241
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document the availability of developer user #492
Comments
Is the |
Yes, but this needs to be also changed in the o/p of |
What are the primary differences between the I suppose one of the real questions here is whether or not we should be documenting the |
the |
When the cluster has been started successfully, we should give the credentials for the 'developer' user in addition to the 'kubeadmin' user. This is related to crc-org#492
When the cluster has been started successfully, we should give the credentials for the 'developer' user in addition to the 'kubeadmin' user. This is related to crc-org#492
When the cluster has been started successfully, we should give the credentials for the 'developer' user in addition to the 'kubeadmin' user. This is related to crc-org#492
When the cluster has been started successfully, we should give the credentials for the 'developer' user in addition to the 'kubeadmin' user. This is related to #492
Is this issue fixed by the commits above? Or do you also want to add the documentation the existence of this user, and when it should be used over admin? |
I have the same interrogations as kevin's regarding |
From Praveen:
|
And use 'developer' instead of 'kubeadmin' when documenting logins to the web console. This fixes crc-org#492
And use 'developer' instead of 'kubeadmin' when documenting logins to the web console. This fixes crc-org#492
And use 'developer' instead of 'kubeadmin' when documenting logins to the web console. This fixes crc-org#492
We now have a
developer
user with passworddeveloper
, this needs to be documented, and maybe the messages printed after start should refer to this instead of using thekubeadmin
user.ref: #395 (comment)
The text was updated successfully, but these errors were encountered: