disable land tag in the backend storage#22507
Conversation
d62abd3 to
cb7f7e3
Compare
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ 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
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
|
@wy65701436 can you add some information in the PR |
can you checkout the commit message? |
|
@wy65701436 updated the PR message as we use this one for the release notes. |
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]>
cb7f7e3 to
f3111ea
Compare
| // 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") |
There was a problem hiding this comment.
Should we have a warning message in the log when the dgst doesn't match the dgt?
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]>
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]>
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]>
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]>
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]>
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]>
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: 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]>
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]>
|
hi @wy65701436, thanks for your contribution! I have two questions I'd like to consult:
|
|
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. |
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: