redhat-developer / redhat-developer/web-terminal-operator
Build for Arm Architectures
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 42
- Forks
- 24
- Avg merge
- 3d 21h
- Merged PRs (30d)
- 1
Description
Is your enhancement related to a problem? Please describe.
I'm always frustrated when I goto the OperatorHub and can't find an Operator when running OpenShift on Arm architectures, which has about 1/10th of the number of available Operators.
Describe the solution you'd like
Looks like the operator itself is built via GitHub Actions? Building for Arm would be a generally low-level update by including the docker/setup-qemu-action@v3 Action and adding platforms: linux/amd64, linux/arm64 to the existing docker/build-push-action
Describe alternatives you've considered
Currently not other alternative outside of building my own Arm arch version.
Additional context
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inspect the existing GitHub Actions workflow that builds the operator and locate its docker/build-push-action step. Read the docker/setup-qemu-action@v3 documentation and compare the current build configuration with the requested linux/amd64 and linux/arm64 platforms. Done means the workflow builds both architectures successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, go
- Domain
- build-system, devops
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100