enable multi-arch build for -reactor and -injector

[toelke]

See #74

I changed the Makefiles to build for the local architecture on make update and build for all specified architectures on make upload.

[rck]

LGTM. As we are not in a rush I guess and with Moritz being the one that oversees the CI parts, I'd wait for him being back from vacation to actually hit the merge button. Guess it is fair to ping him next Tue.

[WanzenBug]

Over all: looks good and I suspect it's working.

Any particular reason we need to use linux/arm64/v8 instead of just linux/arm64, like in the other PRs?

Also, it would be nice to re-use the same workflows as piraeus-client&piraeus-server. I understand that this is a bit harder for drbd-loader, since we have multiple dockerfiles for one "product". However, drbd-reactor should work 1:1 the same as piraeus-server?

[toelke]

For the multiple Dockerfiles it seems as if we would need to have multiple build-blocks in the yaml; I'm not sure if that's nicer than having the loop in the Makefile.

What do you think?

[WanzenBug]

I'd say: "good enough" 😉

LGTM

[WanzenBug]

Apparently not: https://github.com/piraeusdatastore/piraeus/runs/3463516323 😞

[rck]

just some thoughts on where the complexity should be: In general I'd like to see it (hidden) in the Makefiles if possible. They should be easy to use if necessary. Necessary for whatever reason: Somebody just wants a quick rebuild on the command line, or a quick test build. Or switches to another CI pipeline. Maybe one in house. Besides the other points to me it always has a certain degree of vendor lock-in vibes.