Upstream
/
harbor
mirror of https://github.com/goharbor/harbor.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #11098 from jonasrosland/docs-update 

Update a few docs with correct images and formatting
This commit is contained in:
Michael Michael 2020-03-23 10:36:41 -05:00 committed by GitHub
parent 26e3291e41 4adf79c509
commit 4187b375d9
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
5 changed files with 31 additions and 29 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/1.10/administration/configuring-replication/create-replication-endpoints.md
View File

@ -8,6 +8,7 @@ To replicate image repositories from one instance of Harbor to another Harbor or
1. Go to **Registries** and click the **+ New Endpoint** button.
![New replication endpoint](../../../img/replication-endpoint1.png)
1. For **Provider**, use the drop-down menu to select the type of registry to set up as a replication endpoint.
The endpoint can be another Harbor instance, or a non-Harbor registry. Currently, the following non-Harbor registries are supported:
@ -30,6 +31,7 @@ To replicate image repositories from one instance of Harbor to another Harbor or
1. Enter the full URL of the registry to set up as a replication endpoint.
For example, to replicate to another Harbor instance, enter https://harbor_instance_address:443. The registry must exist and be running before you create the endpoint.
1. Enter the Access ID and Access Secret for the endpoint registry instance.
Use an account that has the appropriate privileges on that registry, or an account that has write permission on the corresponding project in a Harbor registry.
@ -38,9 +40,11 @@ To replicate image repositories from one instance of Harbor to another Harbor or
- AWS ECR adapters should use access keys, not a username and password. The access key should have sufficient permissions, such as storage permission.
- Google GCR adapters should use the entire JSON key generated in the service account. The namespace should start with the project ID.
{{< /note >}}
1. Optionally, select the **Verify Remote Cert** check box.
Deselect the check box if the remote registry uses a self-signed or untrusted certificate.
1. Click **Test Connection**.
1. When you have successfully tested the connection, click **OK**.

12
docs/1.10/working-with-projects/project-configuration/_index.md
View File

@ -11,13 +11,13 @@ After the initial creation of a project, you can configure or reconfigure its pr
1. To make all repositories under the project accessible to everyone, select the `Public` checkbox, or deselect this checkbox to make the project private.
1. To prevent un-signed images under the project from being pulled, select the `Enable content trust` checkbox.
![browse project](../../../img/project-configuration.png)
![browse project](../../img/project-configuration.png)
## Searching projects and repositories
Enter a keyword in the search field at the top to list all matching projects and repositories. The search result includes both public and private repositories you have access to.
![browse project](../../../img/new-search.png)
![browse project](../../img/new-search.png)
## Configure Vulnerability Settings in Projects
@ -28,16 +28,16 @@ You can configure projects so that images with vulnerabilities cannot be run, an
1. Select the **Configuration** tab.
1. To prevent vulnerable images under the project from being pulled, select the **Prevent vulnerable images from running** checkbox.
![Prevent vulnerable images from running](../../../img/prevent-vulnerable-images.png)
![Prevent vulnerable images from running](../../img/prevent-vulnerable-images.png)
1. Select the severity level of vulnerabilities to prevent images from running.
![Set vulnerability threshold](../../../img/set-vulnerability-threshold.png)
![Set vulnerability threshold](../../img/set-vulnerability-threshold.png)
Images cannot be pulled if their level is equal to or higher than the selected level of severity. Harbor does not prevent images with a vulnerability severity of `negligible` from running.
1. To activate an immediate vulnerability scan on new images that are pushed to the project, select the **Automatically scan images on push** check box.
![Automatically scan images on push](../../../img/scan-on-push.png)
![Automatically scan images on push](../../img/scan-on-push.png)
## Build history
@ -45,4 +45,4 @@ Build history makes it easy to see the contents of a container image, find the c
In Harbor portal, enter your project, select the repository, click on the link of tag name you'd like to see its build history, the detail page will be opened. Then switch to `Build History` tab, you can see the build history information.
![build history](../../../img/build-history.png)
![build history](../../img/build-history.png)

6
docs/1.10/working-with-projects/using-api-explorer/_index.md
View File

@ -6,9 +6,7 @@ weight: 100
Harbor integrated swagger UI from 1.8. That means all APIs can be invoked through the Harbor interface. You can navigate to the API Explorer in two ways.
1. Log in to Harbor and click the "API EXPLORER" button. All APIs will be invoked with the current user's authorization.
![navigation bar](../../../img/api-explorer-btn.png)
![navigation bar](../../img/api-explorer-btn.png)
2. Navigate to the Swagger page by using the IP address of your Harbor instance and adding the router "devcenter". For example: https://10.192.111.118/devcenter. Then click the **Authorize** button to give basic authentication to all APIs. All APIs will be invoked with the authorized user's authorization.
![authentication](../../../img/authorize.png)
![authentication](../../img/authorize.png)