Harbor Community Meeting Agenda and Notes

We have one bi-weekly recurring Harbor community meeting, at 9 PM UTC +8. We use this meeting to communicate updates to the project, listen to feedback from the Harbor community, and also collect requirements/use cases for new features. Occasionally, we may also host adhoc meetings with a specific agenda. Use the calendar link below to add the recurring meeting to your calendar.

Meeting Link: https://zoom.us/j/734959521

Meeting Agenda: Read, comment, or add agenda items on the meeting notes down below.

Calendar invite: Get calendar invites to the community meetings, office hours, and other events by joining our distribution lists:

Recordings: YouTube Playlist for Harbor Community Meetings

Latest Release plans:https://github.com/goharbor/harbor/wiki/Release-plans

This doc is meant to serve as the “one doc to rule them all” for Harbor community meetings and open discussions.
You can find slides of previous meetings on GitHub. Visit the community details page for schedule, meeting recordings, and additional details.
If you have anything you’d like to put on the agenda, please do so below for the next meeting:

April 16, 2025

Attendees

Topics on Agenda

April 2, 2025

Attendees

Topics on Agenda

  • [Yan] harbor v2.13 GA will be April 11th, and for the 2.14 releases, please prepare your planned feature, we can discuss in the next meeting
  • [Miner] if you have the redis scenario requiremnet, please try the lasted redis feature in 2.13, we need more testing on this and feedbacks are welcome.
  • [Chlins] Demo CNAI model

March 19, 2025

Attendees

Topics on Agenda

March 5, 2025

Topics on Agenda

February 19, 2025

Attendees

Topics on Agenda

February 5, 2025

Attendees

Topics on Agenda

  • https://github.com/goharbor/harbor/pull/21479
  • How can we accelerate the Review of PRs?
    • the maintainers usually review PR weekly and give feedbacks,
    • if all the comments are addressed, the author of PR should ping the reviewer to get review approval and then the maintainer can do the merge.
  • Video recording from KubeCon Na 24, publish on Youtube Channel GoHarbor and goharbor.io website
  • Crossplane provider for Harbor

January 22, 2025

Attendees

Topics on Agenda

AI Summerized Breakdown from Transcript:

This CNCF Harbor community meeting, coordinated by Valim, focused on discussing the upcoming v2.13 release, addressing identified bugs, reviewing feature updates, and discussing community feature requests. The meeting was held online and recorded for public access. Key topics included the v2.13 release timeline, database deadlock issues, garbage collection behavior, UI improvements for pull commands, the single active replication feature, and a community request for enhanced authentication for proxy caches.

Topics Discussed

  1. Harbor v2.13 Release Delay:

    • Discussion about the feature complete date being pushed back due to ongoing work on audit logs and distribution branching integration.
    • Impact of the upcoming Spring Festival holiday on engineering team availability.

  2. Database Deadlock Bug:

    • Identification of a potential database deadlock issue during tag and artifact deletion, particularly with multi-architecture builds and artifact attachments.
    • Possible cause linked to tuple and transaction locks in Postgres when deleting repositories with linked artifacts.
    • Observed in production environments leading to database connection exhaustion.

  3. Garbage Collection Parallelism:

    • Initial concern raised about potential issues with parallel garbage collection jobs, possibly leading to data loss or prolonged execution.
    • Clarification from Yan Wang that garbage collection jobs are queued and executed sequentially by a single worker, not in parallel.

  4. Pull Command UI Update:

    • Prasanth Bupd presented UI enhancements to the "copy pull command" feature.
    • Improvements include adding preferences for container runtimes and custom runtimes, better layout and alignment, and improved user feedback.

  5. Single Active Replication Feature:

    • Valim presented performance test results demonstrating the benefits of single active replication, especially in low-bandwidth environments.
    • Significant performance improvements and reduced data transfer compared to parallel replication executions were highlighted.
    • Code refactoring and encapsulation of logic within the job Monitor observation package were mentioned.

  6. Proxy Cache Authentication/Authorization:

    • Spyridon Trigazis from CERN raised an issue concerning the lack of authentication for proxy cache access, leading to potential security and rate limiting bypass concerns.
    • Proposed extending the visibility levels proposal to include "internal" access for proxy caches.
    • Discussed the need for long-lived tokens or improved robot account management for automated systems to access proxy caches.

  7. Community Infrastructure Automation:

    • Sergio Méndez provided an update on automating the deployment and update processes for the community demo and registry environments in AWS.
    • Work in progress includes scripts for deploying Harbor and core components and implementing a workflow with PR-based approval for infrastructure updates.

  8. Spanish Translation:

    • Sergio Méndez mentioned ongoing work on completing the Spanish translation for Harbor, potentially with assistance from another contributor.

Decisions Made

  • v2.13 Feature Complete Date Shifted: The feature complete date for Harbor v2.13 is officially moved to March 7th. Release Candidate (RC) and General Availability (GA) are expected in the weeks following, targeting early April, potentially around KubeCon.
  • Pull Command UI Feature to be Reviewed for v2.13: Prasanth's updated Pull Command UI feature is considered for inclusion in v2.13 pending code review and demo review by maintainers.
  • Single Active Replication Feature Ready to Merge: The Single Active Replication feature is deemed complete and ready for merging into the codebase.
  • Visibility Levels Proposal to be Extended: The visibility levels proposal will be expanded to incorporate the use case of securing proxy cache access and potentially include user-managed robot accounts for proxy cache scenarios.

Next Steps and Responsibilities

  • Yan Wang:
    • Investigate and attempt to reproduce the database deadlock bug offline, focusing on scenarios involving multi-tag/artifact deletions and artifact attachments.
  • Valim:
    • Provide Yan Wang with concrete steps to reproduce the database deadlock bug.
    • Further investigate garbage collection behavior with a larger dataset to verify sequential execution and identify potential issues related to parallel job submissions.
    • Update the visibility levels proposal to include the user case for securing proxy cache access and potentially user-managed robot accounts, incorporating feedback from Spyridon.
  • Prasanth Bupd:
    • Record a short demo video showcasing the updated Pull Command UI feature and add it to the Pull Request for maintainer review.
  • Maintainers (General):
    • Review Prasanth's code changes and demo video for the Pull Command UI feature to determine its inclusion in v2.13.
    • Review and merge the Single Active Replication feature.
  • Spyridon Trigazis:
    • Provide further input and details to Valim to help extend the visibility levels proposal regarding proxy cache authentication and robot accounts.
  • Sergio Méndez:
    • Continue developing automation scripts for the community infrastructure (demo and registry environments).
    • Continue working on the Spanish translation, potentially collaborating with another contributor.
  • Daniel Jiang:
    • Review the progress of the Spanish translation.





January 8, 2025

Attendees

Notes, Update, Topics

Discussions

December 11, 2024

Attendees

Notes, Update, Topics

Discussions

  • Advanced Artifact Proxying -> Docker Hub has since Nov. lower pull limits. It makes it impossible to use k8s in combination with Docker Hub. The expectation is that users will user Harbor more for this use case. There are quite a few issues with suggestion and bugs in that space.

All previos Archived Meeting notes here:

https://github.com/goharbor/community/wiki/Harbor-Community-Meetings

ShortCuts

Add your shortcut here:
[shortcut_name]: https://url

Select a repo