Pipeline for automatically pushing arm64 images to Harbor is established

Maleware commented 11 months ago

We need to implement an workflow where this runner is used.

Prerequisites:

[x] Build release 23.11.0 manually | issues#483 - we built all operators and all products for ARM once, so we know that it all works.
[x] There is an ARM runner to build on to run the CI

Tasks

### Tasks
- [x] Add a new repo in Harbor the ARM images.
- [ ] https://github.com/stackabletech/issues/issues/552
- [ ] https://github.com/stackabletech/issues/issues/553
- [x] Add missing binaries to Nexus if they are not available for ARM yet. If ARM is not supported, ignore it
- [x] document products for which we cannot support ARM - this might be Superset, Airflow and Listener Operator
- [x] Ubi8-rust-builder multi arch to Harbor

Open Questions

Do we want to only build releases for ARM, or everything?
- good: better dev experience for ARM devs
- bad: more expensive because more build minutes and more storage costs. Basically everything is doubled.

Acceptance Criteria

products
- product images are pushed to Harbor by using a manual triggered GH action
- Products actually work on ARM - If they don't, this is documented
- There is a list of products that we do not support for ARM (if any)
operators
- operator images are build as multi-architecture images and pushed to Harbor

lfrancke commented 10 months ago

Could you change the title of the issue to make sure what it refers to? Place a reference in the text for example "above" is a bit ambiguous :)

Thank you!

Maleware commented 10 months ago

I added the tasks as prerequisites, thanks for pointing it out.

We are currently using a Azure arm64 cluster to keep developing. Means, technically prerequisites are met but not in the way intended.

Tasks will be checked as soon as we have physical hardware.

lfrancke commented 10 months ago

But can you please change the title of the issue as I asked in my previous comment? It contains the word "above" which does not make sense

Maleware commented 9 months ago

The macOS arm64 github runner doesn't look very promising. Moving on to some others:

BuildJet do have a ARM64 runner and Ubuntu https://buildjet.com/for-github-actions/docs/about/pricing
CircleCI have some arm64 runner too https://circleci.com/docs/using-arm/

lfrancke commented 9 months ago

Please only look at BuildJet for now Can you please update the tasklist in the ticket?

Maleware commented 8 months ago

https://github.com/stackabletech/docker-images/pull/600

this is going to conclude this ticket finally.

Maleware commented 8 months ago

This tracks now the progress of the other two tickets. When those are done, this can be reviewed.

Maleware commented 8 months ago

Release 24.3.0 is untested released in stackable-experimental as multi architecture release .

lfrancke commented 7 months ago

Did you update the docs? The tutorial you wrote says that only 23.11 is supported, that's not true anymore.

Maleware commented 7 months ago

I can do it right now. I planned to update docs when I have done basic testing if this is fine for you :)

lfrancke commented 7 months ago

Yep, that sounds good, thanks! I just don't want to be forgotten, thanks for being on top of this.

Maleware commented 6 months ago

This can be closed as all tasks are closed.

stackabletech / issues