upstream/harbor
1
0
Fork 0
mirror of https://github.com/goharbor/harbor synced 2024-09-20 19:29:54 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update _index.md

Browse Source 
Signed-off-by: LandoVMW <ottl@vmware.com>
This commit is contained in:
LandoVMW 2020-05-20 10:17:57 -07:00 committed by LandoVMW
parent f17c0fc4c8
commit 19daf207e9
1 changed files with 12 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
docs/administration/configure-project-quotas/_index.md
View File

@ -3,7 +3,9 @@ title: Configure Project Quotas
weight: 25
---
To exercise control over resource use, as a Harbor system administrator you can set quotas on projects. You can limit the amount of storage capacity that a project can consume. You can set default quotas that apply to all projects globally.
To exercise control over resource usage, as a Harbor system administrator you can set quotas on projects to limit the amount of storage capacity that a project can consume.
You can set default quotas that apply to all projects globally.
{{< note >}}
Default quotas apply to projects that are created after you set or change the default quota. The default quota is not applied to projects that already existed before you set it.
@ -16,17 +18,20 @@ By default, all projects have unlimited quotas for storage use.
1. Select the **Project Quotas** view.
![Project quotas](../../img/project-quota1.png)
1. To set global default quotas on all projects, click **Edit**.
1. To set global default quotas on all projects, click the **Edit** link.
![Project quotas](../../img/project-quota2.png)
1. For **Default storage consumption**, enter the maximum quantity of storage that any project can consume, selecting `MB`, `GB`, or `TB` from the drop-down menu, or enter `-1` to set the default to unlimited.
1. For **Default storage consumption**, enter the maximum quantity of storage that a project can consume.
Specify the number and select the unit (`MB`, `GB`, or `TB`) from the drop-down menu. To set the default to unlimited, enter `-1`.
![Project quotas](../../img/project-quota3.png)
1. Click **OK**.
1. To set quotas on an individual project, select the project and then click **Edit**.
1. To set quotas on an individual project, select the project and then click the **Edit** button.
![Project quotas](../../img/project-quota4.png)
1. For **Default storage consumption**, enter the maximum quantity of storage that this individual project can consume, selecting `MB`, `GB`, or `TB` from the drop-down menu.
1. For **Storage consumption**, enter the maximum quantity of storage that this individual project can consume.
Specify the number and select the unit (`MB`, `GB`, or `TB`) from the drop-down menu. To set the default to unlimited, enter `-1`.
After you set quotas, you can see how much of their quotas each project has consumed.
@ -41,9 +46,9 @@ When setting project quotas, it is useful to know how Harbor calculates storage
{{< note >}}
When users push an image, the manifest is pushed last, after all of the associated blobs have been pushed successfully to the registry. If several images are pushed concurrently and if there is an insufficient number of tags left in the quota for all of them, images are accepted in the order that their manifests arrive. Consequently, an attempt to push an image might not be immediately rejected for exceeding the quota. This is because there was availability in the tag quota when the push was initiated, but by the time the manifest arrived the quota had been exhausted.
{{< /note >}}
- Shared blobs are only computed once per project. In Docker, blob sharing is defined globally. In Harbor, blob sharing is defined at the project level. As a consequence, overall storage usage can be greater than the actual disk capacity.
- Shared blobs are computed only once per project. In Docker, blob sharing is defined globally. In Harbor, blob sharing is defined at the project level. As a consequence, overall storage usage can be greater than the actual disk capacity.
- Retagging images reserves and releases resources:
- If you retag an image within a project, the storage usage does not change because there are no new blobs or manifests.
- If you retag an image from one project to another, the storage usage will increase.
- If you retag an image from one project to another, the storage usage increases.
- During garbage collection, Harbor frees the storage used by untagged blobs in the project.
- Helm chart size is not calculated.