Skip to content

disable land tag in the backend storage#22507

Merged
wy65701436 merged 2 commits into
goharbor:mainfrom
wy65701436:do-not-land-tag
Nov 6, 2025
Merged

disable land tag in the backend storage#22507
wy65701436 merged 2 commits into
goharbor:mainfrom
wy65701436:do-not-land-tag

Conversation

@wy65701436

@wy65701436 wy65701436 commented Oct 27, 2025

Copy link
Copy Markdown
Contributor

Thank you for contributing to Harbor!
disable land tag in the backend storage
According to the gc performance proposal, harbor will skip to write the tag file into the data storage since we already use the harbor database to manage the tag CRUD.
Proposal: goharbor/community#265

fixed #22405

Please indicate you've done the following:

  • Well Written Title and Summary of the PR
  • Label the PR as needed. "release-note/ignore-for-release, release-note/new-feature, release-note/update, release-note/enhancement, release-note/community, release-note/breaking-change, release-note/docs, release-note/infra, release-note/deprecation"
  • Accepted the DCO. Commits without the DCO will delay acceptance.
  • Made sure tests are passing and test coverage is added if needed.
  • Considered the docs impact and opened a new docs issue or PR with docs changes if needed in website repository.

@codecov

codecov Bot commented Oct 27, 2025

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 75.00000% with 5 lines in your changes missing coverage. Please review.
✅ Project coverage is 65.84%. Comparing base (c8c11b4) to head (b69eace).
⚠️ Report is 594 commits behind head on main.

Files with missing lines Patch % Lines
src/server/registry/manifest.go 75.00% 3 Missing and 2 partials ⚠️
Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff             @@
##             main   #22507       +/-   ##
===========================================
+ Coverage   45.36%   65.84%   +20.47%     
===========================================
  Files         244     1073      +829     
  Lines       13333   116095   +102762     
  Branches     2719     2931      +212     
===========================================
+ Hits         6049    76440    +70391     
- Misses       6983    35418    +28435     
- Partials      301     4237     +3936     
Flag Coverage Δ
unittests 65.84% <75.00%> (+20.47%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
src/server/registry/manifest.go 68.15% <75.00%> (ø)

... and 986 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@OrlinVasilev

Copy link
Copy Markdown
Member

@wy65701436 can you add some information in the PR

@wy65701436

Copy link
Copy Markdown
Contributor Author

@wy65701436 can you add some information in the PR

can you checkout the commit message?

@OrlinVasilev

Copy link
Copy Markdown
Member

@wy65701436 updated the PR message as we use this one for the release notes.

@chlins chlins left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

According to the gc performance proposal, harbor will skip to write the tag file into the data storage since we already use the harbor database to manage the tag CRUD.
Proposal: goharbor/community#265

fixed goharbor#22405

Signed-off-by: wang yan <[email protected]>
// the reference is tag, get the digest from the response header
if _, err = digest.Parse(reference); err != nil {
if _, err := digest.Parse(reference); err != nil {
dgt = buffer.Header().Get("Docker-Content-Digest")

@stonezdj stonezdj Nov 6, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we have a warning message in the log when the dgst doesn't match the dgt?

@wy65701436
wy65701436 enabled auto-merge (squash) November 6, 2025 10:43
@wy65701436
wy65701436 merged commit 95003aa into goharbor:main Nov 6, 2025
12 checks passed
Aloui-Ikram pushed a commit to Aloui-Ikram/harbor that referenced this pull request Nov 19, 2025
According to the gc performance proposal, harbor will skip to write the tag file into the data storage since we already use the harbor database to manage the tag CRUD.
Proposal: goharbor/community#265

fixed goharbor#22405

Signed-off-by: wang yan <[email protected]>
Co-authored-by: wang yan <[email protected]>

Signed-off-by: Ikram Aloui <[email protected]>
Aloui-Ikram pushed a commit to Aloui-Ikram/harbor that referenced this pull request Nov 19, 2025
According to the gc performance proposal, harbor will skip to write the tag file into the data storage since we already use the harbor database to manage the tag CRUD.
Proposal: goharbor/community#265

fixed goharbor#22405

Signed-off-by: wang yan <[email protected]>
Co-authored-by: wang yan <[email protected]>

Signed-off-by: Aloui-Ikram <[email protected]>
Aloui-Ikram pushed a commit to Aloui-Ikram/harbor that referenced this pull request Nov 19, 2025
According to the gc performance proposal, harbor will skip to write the tag file into the data storage since we already use the harbor database to manage the tag CRUD.
Proposal: goharbor/community#265

fixed goharbor#22405

Signed-off-by: wang yan <[email protected]>
Co-authored-by: wang yan <[email protected]>

Signed-off-by: Aloui-Ikram <[email protected]>
Signed-off-by: ikram aloui <[email protected]>
Aloui-Ikram pushed a commit to Aloui-Ikram/harbor that referenced this pull request Nov 19, 2025
According to the gc performance proposal, harbor will skip to write the tag file into the data storage since we already use the harbor database to manage the tag CRUD.
Proposal: goharbor/community#265

fixed goharbor#22405

Signed-off-by: wang yan <[email protected]>
Co-authored-by: wang yan <[email protected]>

Signed-off-by: Aloui-Ikram <[email protected]>
Signed-off-by: ikram aloui <[email protected]>
Signed-off-by: Aloui-Ikram <[email protected]>
Aloui-Ikram pushed a commit to Aloui-Ikram/harbor that referenced this pull request Nov 19, 2025
According to the gc performance proposal, harbor will skip to write the tag file into the data storage since we already use the harbor database to manage the tag CRUD.
Proposal: goharbor/community#265

fixed goharbor#22405

Signed-off-by: wang yan <[email protected]>
Co-authored-by: wang yan <[email protected]>

Signed-off-by: Aloui-Ikram <[email protected]>
Signed-off-by: ikram aloui <[email protected]>
Signed-off-by: Aloui-Ikram <[email protected]>
Aloui-Ikram pushed a commit to Aloui-Ikram/harbor that referenced this pull request Nov 19, 2025
According to the gc performance proposal, harbor will skip to write the tag file into the data storage since we already use the harbor database to manage the tag CRUD.
Proposal: goharbor/community#265

fixed goharbor#22405

Signed-off-by: wang yan <[email protected]>
Co-authored-by: wang yan <[email protected]>

Signed-off-by: Aloui-Ikram <[email protected]>
Aloui-Ikram pushed a commit to Aloui-Ikram/harbor that referenced this pull request Nov 19, 2025
According to the gc performance proposal, harbor will skip to write the tag file into the data storage since we already use the harbor database to manage the tag CRUD.
Proposal: goharbor/community#265

fixed goharbor#22405

Signed-off-by: wang yan <[email protected]>
Co-authored-by: wang yan <[email protected]>

Signed-off-by: Aloui-Ikram <[email protected]>
Aloui-Ikram pushed a commit to Aloui-Ikram/harbor that referenced this pull request Nov 24, 2025
Signed-off-by: dulanting <[email protected]>
Signed-off-by: Aloui-Ikram <[email protected]>

Add unit test for DeleteManifest method in TencentCR adapter (goharbor#22537)

Added test case

Signed-off-by: Anurag Ojha <[email protected]>
Signed-off-by: Aloui-Ikram <[email protected]>

disable land tag in the backend storage (goharbor#22507)

According to the gc performance proposal, harbor will skip to write the tag file into the data storage since we already use the harbor database to manage the tag CRUD.
Proposal: goharbor/community#265

fixed goharbor#22405

Signed-off-by: wang yan <[email protected]>
Co-authored-by: wang yan <[email protected]>

Signed-off-by: Aloui-Ikram <[email protected]>
vg006 pushed a commit to vg006/harbor that referenced this pull request Dec 4, 2025
According to the gc performance proposal, harbor will skip to write the tag file into the data storage since we already use the harbor database to manage the tag CRUD.
Proposal: goharbor/community#265

fixed goharbor#22405

Signed-off-by: wang yan <[email protected]>
Co-authored-by: wang yan <[email protected]>
@microyahoo

Copy link
Copy Markdown
Contributor

hi @wy65701436, thanks for your contribution! I have two questions I'd like to consult:

  1. I see this PR targets version 2.15. Why isn't it being merged into version 2.13 or 2.14?
  2. If older versions of Harbor are upgraded to a version containing this PR, will there be any compatibility issues? Because there are also changes in the underlying storage.

@jsingleton785

Copy link
Copy Markdown

Can we have an optional disable for this feature. My team relies on the tags being in the S3 storage to pulls directly from the S3 bucket in Disaster Recovery scenarios. Without the tag links, we cannot pull images when Harbor is down.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Completed

Development

Successfully merging this pull request may close these issues.

Skip the tag landing on artifact pushing

8 participants