Repository navigation
WTO-615: Add arm64 (aarch64) support to operator metadata and local build - #208
Merged
Merged
Conversation
…uild - Add OLM arch labels (arch.amd64, arch.arm64, os.linux) to the CSV so OLM advertises multi-arch support; these propagate downstream via the operator-metadata submodule sync. - Remove the hardcoded --platform=linux/amd64 from build_controller_image so local/manual image builds honor the target architecture. The Go build is already arch-clean (GOARCH, CGO_ENABLED=0). Refs: WTO-615, OCPSTRAT-3873, HPSTRAT-705 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: Badre Tejado-Imam <btejado@redhat.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #208 +/- ##
=======================================
Coverage 55.78% 55.78%
=======================================
Files 5 5
Lines 346 346
=======================================
Hits 193 193
Misses 151 151
Partials 2 2
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
Collaborator
Author
|
Part of the WTO-615 arm64 set (downstream GitLab MRs):
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds the upstream pieces of arm64 (aarch64) enablement for the Web Terminal Operator:
operatorframework.io/arch.amd64,operatorframework.io/arch.arm64, andoperatorframework.io/os.linux(allsupported) tometadata.labelsin the ClusterServiceVersion, so OLM advertises multi-arch support. These propagate downstream via the operator-metadata submodule sync.--platform=linux/amd64from thebuild_controller_imagetarget incontroller.mkso local/manual image builds honor the target architecture. The Go build is already arch-clean (GOARCH,CGO_ENABLED=0).Why
Part of the HPBU arm64 mandate (HPSTRAT-705 / OCPSTRAT-3873): every applicable operator and its operands must ship
amd64+aarch64and run on Graviton-only ROSA HCP.Scope / notes
web-terminal-operatorrepo.Testing
controller.mkvalidated locally; no functional change to the amd64 path.Refs: WTO-615, OCPSTRAT-3873, HPSTRAT-705
🤖 Generated with Claude Code