| title | author | date | draft | showPageInfo | ||
|---|---|---|---|---|---|---|
Harbor v2.7 release features |
|
2022-12-19 12:00:00 +0400 |
false |
true |
We're delighted to announce the general availability of Harbor v2.7.0.
Add the job service dashboard to monitor and control the job queues/schedules/workers
- Add jobservice monitoring api list pool, worker and stop running task by @stonezdj in 17658
- feat: support customize session timeout by @chlins in 17767
- Add REST API to list job queue status, pause/resume job queue and list schedulers by @stonezdj in 17707
- Add Jobservice UI by @AllForNothing in 17722
The job service dashboard is a web-based interface that allows you to view and manage jobs that are running in the Harbor job service. It is available at https://<harbor_url>/harbor/job-service-dashboard/. You can use the dashboard to view the status of job queues, the schedule of jobs, and the status of the job service pools and workers. you can also use it to stop pending or running jobs, or pause or resume the job service queue.
- Log in to the Harbor Web interface with an account that has Harbor system administrator privileges.
- Expand Administration, and select Job Service Dashboard.
In the job service dashboard, you can view the status of the job service queue, the job service pools, and the job service workers.
The following table describes the information that is displayed in the dashboard.
| Field | Description | Actions |
|---|---|---|
| Pending Jobs In Queues | The job service queue is a FIFO queue that stores jobs to be executed. Total displays the count of queue type, and the top 2 queues | Stop All: stop all jobs in all queues |
| Schedules | The job service pool is a pool of workers that execute jobs, display the total count of schedules and show its status | Pause All: Pause all running job schedule, Resume All: Resume all paused job schedule |
| Workers | The job service worker is a goroutine that executes jobs, it displays the free/total workers | Free All: stop the execution of running jobs to free all workers |
In the job service dashboard, click the Job Queues tab.
The Job Queues tab displays the detail of job queues. The following table describes the information that is displayed in the Job Queues tab.
| Field | Description |
|---|---|
| Job Type | The name of the job queue. |
| Pending Count | The number of jobs that are waiting to be executed in the queue. |
| Latency | The waiting time of the current queue, it indicate how long tasks in the queue have already waited. |
| Paused | The paused status of job queue. |
You can check full proposal here
Full documentation here
Support copy over chunk when copying image blobs for harbor replication.
- feat: introduce the copy by chunk for replication by @chlins in 17602
- Add copy_by-chunk checkbox for replication rule by @AllForNothing in 17617
With the development of edge compute, the image registry such as Harbor be deployed by sink to edge nodes to achieve the better performance and independence. For some use cases, they need to replicate images from one center Harbor(regisgtry) to edge Harbor instance, but usually the network for edge is restrict and even unstable. The Low Bandwidth and High Latency environment is the big challenge for replication. So we need to support copy over chunk for replication to improve the quality.
You can check full proposal here
- Add session timeout input by @AllForNothing in 17769
- Add JFrog Artifactory As Supported Proxy-Cache Registry Source by @erismaster in 17738
- Sort group search result by most match order by @stonezdj in 17708
- Start the deprecation of Chartmuseum from v2.6.0 and begin to remove in v2.8.0. More details, please refer to the discussion.
- Start the deprecation of Notary(signer&server) from v2.6.0 and begin to remove in v2.8.0. More details, please refer to the discussion.
- Remove email config page by @AllForNothing in 17711
If you're a user of Harbor and want to share any feedback, we'd love to hear from you here!
Huge shoutout to the maintainer team, our contributors & everyone in the community who helped the project realize its level of adoption today !! The project would not be where it is today without the community
We also want to thank the following users for their sustained contributions to the project!
Thank you to all who contributed to 2.7 full release notes here
- @tmaroschik made their first contribution in goharbor/harbor#16442
- @wujunwei made their first contribution in goharbor/harbor#16206
- @lengrongfu made their first contribution in goharbor/harbor#17306
- @mrbusche made their first contribution in goharbor/harbor#17303
- @vincentni made their first contribution in goharbor/harbor#17533
- @gaius-qi made their first contribution in goharbor/harbor#17581
- @Juneezee made their first contribution in goharbor/harbor#17670
- @94rain made their first contribution in goharbor/harbor#17718
- @erismaster made their first contribution in goharbor/harbor#17738
- @yanggangtony made their first contribution in goharbor/harbor#17792
- @akhilerm made their first contribution in goharbor/harbor#17818
- @sayaoailun made their first contribution in goharbor/harbor#16641
Get updates on Twitter: @project_harbor
Chat with us on Slack: #harbor
and #harbor-dev
on theCNCF Slack
Collaborate with us on GitHub
Attend the community meetings
Orlin Vasilev
Harbor Community Manager
GitHub: @OrlinVasilev
Twitter: @OrlinVasilev