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
(docker registry access) add a first step to create a regular user, with example #1050
Conversation
@@ -239,7 +239,17 @@ this repository via an image. | |||
To access the registry directly, such as to perform `docker push` or `docker pull` operations, you | |||
must first log in to the registry using an access token. | |||
|
|||
. Ensure you are logged in to OpenShift as a link:../../architecture/core_concepts/projects_and_users.html#users[regular user]: | |||
. Create a link:../../architecture/core_concepts/projects_and_users.html#users[regular user], for example, with `HTPASSWD` authentication: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since they may have already created or have access to a regular user, or chosen a different identity provider, suggest something like:
If a link:../../architecture/core_concepts/projects_and_users.html#users[regular user] does not already exist, create one according to your chosen link:../../admin_guide/configuring_authentication.html[identity provider]. For example, if you are using htpasswd
authentication:
@rjhowe BTW, the pretty render is at: |
@rjhowe @adellape
|
@tnguyen-rh Based on latest comment, my understanding is you wanted to continue working on this, right? If I've misunderstand, you can undo my [WIP]-titling. |
@adellape |
@tnguyen-rh When you say proposed rework. Are we talking about having a separate section that goes into detail regarding the registry? |
@rjhowe |
Looks good. |
ed57d96
to
d2dc4ae
Compare
@adellape Squashed, rebased. Ready to merge (pending travis). |
@@ -20,6 +20,18 @@ link:../../architecture/infrastructure_components/image_registry.html#integrated | |||
Docker registry] that can be deployed in your OpenShift environment to locally | |||
manage images. | |||
|
|||
To make full use of the registry, you must create a link:../../architecture/core_concepts/projects_and_users.html#users[regular user] with the `system:registry` role, if one does not already exist, using your preferred link:../../admin_guide/configuring_authentication.html[identity provider]. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's some inconsistent markup between roles and users mentioned in the topic. E.g., compare system:registry, system:image-builder, system:admin, etc. They should probably be the same; the precedent was using plain bold as "system items" (fuzzy, I know).
@tnguyen-rh Some comments inline. Looking good. BTW, there are some new lines that have not been wrapped at 80, as well. |
d2dc4ae
to
1c84b09
Compare
1c84b09
to
b5d9bba
Compare
@adellape Thanks for the review. I've updated accordingly (plus squash and rebase). |
(docker registry access) add a first step to create a regular user, with example
@rjhowe @adellape
This is for BZ 1248706.