[Housekeeping] Produce multi-arch images in CI/CD pipelines

[hajapy]

Describe the issue

Update the build pipelines to also produce arm64 images.

At a glance, I think these workflows would need to be updated:

https://github.com/flyteorg/flytetools/blob/master/.github/workflows/docker_build.yml#L34
https://github.com/flyteorg/flytetools/blob/master/.github/workflows/publish.yml#L36
https://github.com/flyteorg/flyte/blob/master/.github/workflows/create_release.yml

I would suggest to look into using the official docker actions if possible:

https://github.com/docker/setup-buildx-action
https://github.com/docker/build-push-action

What if we do not do this?

Unable to use official flyte images on arm64 instances. Users would need to build their own images of all the flyte control plane components.

Related component(s)

No response

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes

[prabhu43]

Hi,
I am interested to pick this up

[prabhu43]

Hi
I could not find the usage of this workflow https://github.com/flyteorg/flytetools/blob/master/.github/workflows/docker_build.yml.

Can someone help me to gain some context?

[prabhu43]

@eapolinario I changed 2 workflows in flytetools to publish multi-arch images.
Since https://github.com/flyteorg/flyte/blob/master/.github/workflows/create_release.yml does not have docker build step, its not applicable there.

Please review this PR for flytetools flyteorg/flytetools#66

[wild-endeavor]

@hajapy which images specifically are you referring to? I didn't know this issue was being worked on but others in the community already made changes to the flytekit, flyte-binary and sandbox-bundled images.

[hajapy]

@wild-endeavor I was referring to flyteadmin, flytepropeller, datacatalog, flytescheduler and flyteconsole (as well as the -release copies)