Design for multi-arch build and windows build

[Lyndon-Li]

For issue #8429. Add the design for multi-arch build and windows build

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 59.00%. Comparing base (af85b7d) to head (298b497).
Report is 14 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #8459      +/-   ##
==========================================
+ Coverage   58.98%   59.00%   +0.02%     
==========================================
  Files         368      368              
  Lines       39000    39015      +15     
==========================================
+ Hits        23004    23022      +18     
+ Misses      14532    14530       -2     
+ Partials     1464     1463       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[kaovilai]

This makes sense to me.

[kaovilai]

For reference, we had done something with manifest lists earlier here. Note that we had disabled Travis-CI but .travis.yml here was last working for us.

velero/.travis.yml

Lines 64 to 77 in fe3907e

	docker manifest create \
	${IMAGE1}:${TAG} \
	${IMAGE1}:${TAG}-amd64 \
	${IMAGE1}:${TAG}-ppc64le \
	${IMAGE1}:${TAG}-s390x \
	${IMAGE1}:${TAG}-aarch64
	docker manifest create \
	${IMAGE2}:${TAG} \
	${IMAGE2}:${TAG}-amd64 \
	${IMAGE2}:${TAG}-ppc64le \
	${IMAGE2}:${TAG}-s390x \
	${IMAGE2}:${TAG}-aarch64
	docker manifest push ${IMAGE1}:${TAG}
	docker manifest push ${IMAGE2}:${TAG}

[kaovilai]

Will the linux manifest list cover s390x? #2622

[Lyndon-Li]

Will the linux manifest list cover s390x? #2622

It is not in the plan. Supporting a new platform not only means support of build, but also installation and running. There is no plan to support all of these for s390.

[kaovilai]

The manifest list already work with that. There's no code change at all to install or run when image is a manifest list containing Linux/s390x

[Lyndon-Li]

The manifest list already work with that. There's no code change at all to install or run when image is a manifest list containing Linux/s390x

By running, I mean have Velero running on the specific platform, we need to test to identify the gaps and make fixes. For s390 we have no plan nor env to do this.

[Lyndon-Li]

Made some further changes:

1. Removed BUILDX_TAG_GCR input parameter in design
2. Added build to tar for Local Build

[reasonerjt]

lgtm, thanks!

[kaovilai]

Want to note that nanoserver insider has arm. There are not yet GA Windows base images with arm that I can see however.
https://hub.docker.com/r/microsoft/windows-nanoserver-insider
https://mcr.microsoft.com/v2/windows/nanoserver/insider/tags/list

[Lyndon-Li]

As mentioned here, we will consider to support arm for Windows until it is officially supported by Windows container and other major components like Hyper-V, .Net, etc. The build of arm based client or image itself is not a problem