preheat image supports authentication and parse multi manifest mediatype

[Panlq]

Description

1. support preheat images from private registry correctly
2. parse multi-mediatype manifest
3. support specific platforms for manifest list

Related Issue

#769

Motivation and Context

Supports direct preheating of private registry images

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation Update (if none of the other choices apply)

Checklist

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.

[gaius-qi]

@Panlq Please fix lint.

[Panlq]

@Panlq Please fix lint.
https://github.com/dragonflyoss/Dragonfly2/actions/runs/6601592490/job/18066447978
It seems that the execution of the lint timeout. I have fixed the lint during the first action execution.

[codecov]

Codecov Report

Merging #2819 (eaf60e9) into main (2515c13) will decrease coverage by 0.53%.
Report is 5 commits behind head on main.
The diff coverage is 65.78%.

@@            Coverage Diff             @@
##             main    #2819      +/-   ##
==========================================
- Coverage   52.08%   51.55%   -0.53%     
==========================================
  Files         157      162       +5     
  Lines       21364    21851     +487     
==========================================
+ Hits        11127    11265     +138     
- Misses       9590     9921     +331     
- Partials      647      665      +18     

Flag	Coverage Δ
Object-compatibility-e2etests	?
e2etests	?
unittests	51.55% <65.78%> (-0.53%)	⬇️

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

Files	Coverage Δ
manager/job/types.go	30.76% <30.76%> (ø)
manager/job/preheat.go	43.15% <72.52%> (ø)
manager/job/image_auth_client.go	63.95% <63.95%> (ø)

... and 3 files with indirect coverage changes

[gaius-qi]

@Panlq Please add E2E testing in https://github.com/dragonflyoss/Dragonfly2/blob/main/test/e2e/manager/preheat.go.

[Panlq]

@Panlq Please add E2E testing in https://github.com/dragonflyoss/Dragonfly2/blob/main/test/e2e/manager/preheat.go.

Changes in new features are compatible with the original e2e test content！so there is no need to add anything else？
This PR only affects the image type and does not affect the file type preheating tasks.
I have added unit tests for the image type:
https://github.com/dragonflyoss/Dragonfly2/pull/2819/files#diff-081c3a63e6dd230c53072d96260e02bab12cb187c4d75b018c2c0052652a951a

[gaius-qi]

@Panlq Please add E2E testing in https://github.com/dragonflyoss/Dragonfly2/blob/main/test/e2e/manager/preheat.go.

Changes in new features are compatible with the original e2e test content！so there is no need to add anything else？ This PR only affects the image type and does not affect the file type preheating tasks. I have added unit tests for the image type: https://github.com/dragonflyoss/Dragonfly2/pull/2819/files#diff-081c3a63e6dd230c53072d96260e02bab12cb187c4d75b018c2c0052652a951a

@Panlq Unit testing and E2E testing are two different things. Please add E2E testing in https://github.com/dragonflyoss/Dragonfly2/blob/main/test/e2e/manager/preheat.go and resolved conflicting.

[Panlq]

I know, what I want to express is that the original e2e has already involved image type testing, and is also compatible with new code.

I am familiar with the existing e2e use cases and add the scenario of specifying platform parameters. The auth(account and password) cannot be written in them

[gaius-qi]

I know, what I want to express is that the original e2e has already involved image type testing, and is also compatible with new code.

I am familiar with the existing e2e use cases and add the scenario of specifying platform parameters. The auth(account and password) cannot be written in them

You can send me the image, and I will upload it to dragonfly's group in docker hub for E2E testing. I think you should need to add multi-platform E2E test cases.

[gaius-qi]

I know, what I want to express is that the original e2e has already involved image type testing, and is also compatible with new code.

I am familiar with the existing e2e use cases and add the scenario of specifying platform parameters. The auth(account and password) cannot be written in them

@Panlq
First you can send me the image and version, and I will upload it to dragonfly's group in docker hub for E2E testing. I think you should need to add multi-platform E2E test cases.

[Panlq]

I know, what I want to express is that the original e2e has already involved image type testing, and is also compatible with new code.
I am familiar with the existing e2e use cases and add the scenario of specifying platform parameters. The auth(account and password) cannot be written in them

@Panlq First you can send me the image and version, and I will upload it to dragonfly's group in docker hub for E2E testing. I think you should need to add multi-platform E2E test cases.

ok, I think I can use busybox:latest (amd64/arm64) to write e2e use cases

[gaius-qi]

I know, what I want to express is that the original e2e has already involved image type testing, and is also compatible with new code.
I am familiar with the existing e2e use cases and add the scenario of specifying platform parameters. The auth(account and password) cannot be written in them

@Panlq First you can send me the image and version, and I will upload it to dragonfly's group in docker hub for E2E testing. I think you should need to add multi-platform E2E test cases.

ok, I think I can use busybox:latest (amd64/arm64) to write e2e use cases

You can use dragonflyoss/scheduler:v2.1.0(amd64/arm64) to write e2e use cases.

[Panlq]

ok, I have added the e2e test case, please re-execute ci! @gaius-qi

[gaius-qi]

LGTM