Ordering Container Registry Access¶
We create Harbor projects and credentials for you. Once you have a project, you push and pull images in it yourself. This page describes how to order a project and which options you can choose.
How to Order¶
Open a ticket in our Service Desk. State that you want a Container Registry project and include the information below.
Information to Include¶
| Field | Required | Description | Example |
|---|---|---|---|
| Project name | Yes | The name of the Harbor project. It becomes part of every image path. | my-team |
| Users | Yes | The people who need access, and whether each one can push or only pull. | Two developers with push access |
| Machine accounts | No | Accounts for CI pipelines or clusters, and whether each one can push or only pull. | One push account for CI |
| Storage quota | No | The storage limit for the project. See Options. | 50 GiB |
| Technical contact | Yes | The person we contact about the project. | Name and email |
Options¶
| Option | Choices | Guidance |
|---|---|---|
| Storage quota | Size in GiB | Pushes fail when the project reaches its quota. Retention rules keep usage under control. |
| Visibility | Private | Only authenticated accounts with access to the project can pull from a private project. |
| Vulnerability scanning | On push | Harbor scans images for known vulnerabilities. A project can also block pulls of images above a chosen severity. |
| Tag retention | None, or rules by count or age | Retention rules delete old tags automatically, for example keeping the last 10 tags per repository. |
What You Receive¶
When the project is ready, we give you:
- A username and password for each user and machine account.
- The project path in the registry, which you use as the image prefix.
Changes and Cancellation¶
To add or remove accounts, change the quota or retention, or remove a project, open a new Service Desk ticket that names the project and the change you need.
Next Steps¶
- Getting Started shows how to log in, push and pull images.