Skip to content
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

Closed
anjannath opened this issue Aug 28, 2019 · 7 comments
Closed

Document the availability of developer user #492

anjannath opened this issue Aug 28, 2019 · 7 comments
Labels
kind/documentation Documentation issues.

Comments

@anjannath
Copy link
Member

We now have a developer user with password developer, this needs to be documented, and maybe the messages printed after start should refer to this instead of using the kubeadmin user.

ref: #395 (comment)

@anjannath anjannath added the kind/documentation Documentation issues. label Aug 28, 2019
@kowen-rh
Copy link
Contributor

Is the developer user the one that we should generally recommend logging in as after running crc start? I'm assuming "yes", but would like to be sure. :)

@anjannath
Copy link
Member Author

anjannath commented Aug 28, 2019

Is the developer user the one that we should generally recommend logging in as after running crc start?

Yes, but this needs to be also changed in the o/p of crc start currently we are printing the kubeadmin user credentials, and the oc login command also uses the kubeadmin user.

@kowen-rh
Copy link
Contributor

What are the primary differences between the developer user and the kubeadmin user? Why would one be used instead of the other?

I suppose one of the real questions here is whether or not we should be documenting the kubeadmin user at all, and if we do document kubeadmin, in what contexts does that user apply?

@anjannath
Copy link
Member Author

the kubeadmin user is the cluster admin, kind of the root user for the cluster, it has access to all the namespace, the developer user is a bit restricted by default that it does not have access to the existing namespaces, it'll have access to namespaces that are created by himself, but it can also perform admin level actions by impersonating as a cluster admin, by passing in --as=system:admin to oc commands.

cfergeau added a commit to cfergeau/crc that referenced this issue Aug 29, 2019
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
cfergeau added a commit to cfergeau/crc that referenced this issue Aug 30, 2019
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
cfergeau added a commit to cfergeau/crc that referenced this issue Sep 2, 2019
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
praveenkumar pushed a commit that referenced this issue Sep 3, 2019
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
@cfergeau
Copy link
Contributor

What are the primary differences between the developer user and the kubeadmin user? Why would one be used instead of the other?

I suppose one of the real questions here is whether or not we should be documenting the kubeadmin user at all, and if we do document kubeadmin, in what contexts does that user apply?

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?

@cfergeau
Copy link
Contributor

cfergeau commented Sep 26, 2019

I have the same interrogations as kevin's regarding developer VS kubeadmin.
When should one be using kubeadmin?
When should one be using developer?
If I want to create/install an application on my crc cluster, can I do it as developer or do I need to be kubeadmin?

@cfergeau
Copy link
Contributor

From Praveen:

If a user want to administrate the cluster he/she should use kubeadmin user (like creating new users, setting the roles ..etc, installing some operators ..etc.) Just creating or deploying an application, developer user would be good enough.

cfergeau added a commit to cfergeau/crc that referenced this issue Sep 30, 2019
And use 'developer' instead of 'kubeadmin' when documenting logins to the web
console.

This fixes crc-org#492
cfergeau added a commit to cfergeau/crc that referenced this issue Oct 1, 2019
And use 'developer' instead of 'kubeadmin' when documenting logins to the web
console.

This fixes crc-org#492
cfergeau added a commit to cfergeau/crc that referenced this issue Oct 2, 2019
And use 'developer' instead of 'kubeadmin' when documenting logins to the web
console.

This fixes crc-org#492
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/documentation Documentation issues.
Projects
None yet
Development

No branches or pull requests

3 participants