Skip to content

feat(CORE-4981): add multi-arch toggle to gitops template - #496

Merged
kaitimmer merged 2 commits into
mainfrom
core-4981-multi-arch-builds
Sep 3, 2026
Merged

feat(CORE-4981): add multi-arch toggle to gitops template#496
kaitimmer merged 2 commits into
mainfrom
core-4981-multi-arch-builds

Conversation

@kaitimmer

@kaitimmer kaitimmer commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

What changed

New multi-arch input (boolean, default false) on template_gitops.yml. When enabled, the template fans out into a build matrix (amd64 on ubuntu-24.04, arm64 on ubuntu-24.04-arm) using multiarch-mode: build, then a merge job combines the digests via multiarch-mode: merge and runs the GitOps/Upwind steps as usual.

Callers that do not set it keep the existing single gitops job, unchanged and still pinned to v8.0.1 — same job id, same display name, so required status checks are unaffected.

multiarch-artifact-name is exposed too, so workflows building more than one image can keep their digests apart.

Why it changed

Recovery/failover regions have no ARM capacity, so images deployed there must ship both linux/amd64 and linux/arm64. Wiring the matrix into the shared template means consumers flip one boolean instead of restructuring their workflow.

How to test it

Used here: https://github.com/Staffbase/slo-operator/pull/37

Screenshot 2026-09-02 at 16 32 39

yamllint .github/workflows/ passes. End to end: point a test repo at this branch with multi-arch: true and verify docker buildx imagetools inspect <tag> lists both platforms — being validated now via Staffbase/slo-operator.


The changes and/or the PR description has generated by with the help of OpenCode.

@kaitimmer kaitimmer added the do not merge Pull requests that should not be merged label Aug 31, 2026
…v8.2.1

gitops-github-action#159 merged and released as v8.2.1. Swap the
placeholder branch-SHA pins on the new multi-arch build/merge jobs to
the release tag, as noted in the PR's blocked-on section.
@kaitimmer kaitimmer removed the do not merge Pull requests that should not be merged label Sep 2, 2026
@kaitimmer
kaitimmer marked this pull request as ready for review September 2, 2026 14:33
@kaitimmer
kaitimmer requested a review from a team as a code owner September 2, 2026 14:33
@kaitimmer
kaitimmer requested review from a team, 0x46616c6b, axdotl and ricoberger and removed request for a team September 2, 2026 14:33

@0x46616c6b 0x46616c6b left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you please label the PR properly for the release?

@kaitimmer kaitimmer added the enhancement New feature or request label Sep 3, 2026
@kaitimmer
kaitimmer requested a review from 0x46616c6b September 3, 2026 11:20
@0x46616c6b 0x46616c6b added the minor Pull requests with new features label Sep 3, 2026
@kaitimmer
kaitimmer merged commit 253a50e into main Sep 3, 2026
8 checks passed
@kaitimmer
kaitimmer deleted the core-4981-multi-arch-builds branch September 3, 2026 13:33
@github-actions github-actions Bot locked and limited conversation to collaborators Sep 3, 2026
@soemo

soemo commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

enhancement New feature or request minor Pull requests with new features

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants