Recent articles
Harbor v2.11 release - The SBOMs release
Bonjour Harbor KubeCon + CloudNativeCon Europe 2024 - Paris
Harbor v2.10 release
Harbor Recap from KubeCon Chicago 2023
Harbor v2.7 release features
December 19, 2022
Orlin Vasilev
Add the job service dashboard to monitor and control the job queues/schedules/workers
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.
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.
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
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
Get updates on Twitter:
@project_harbor
Chat with us on Slack:
#harbor
and
#harbor-dev
on the
CNCF Slack
Collaborate with us on
GitHub
Attend the
community meetings
Orlin Vasilev
Harbor Community Manager
GitHub:
@OrlinVasilev
Twitter:
@OrlinVasilev