openshift / openshift/oadp-operator
OADP-1.3 multiarch deploy-olm
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 92
- Forks
- 93
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 43
Description
Is your feature request related to a problem? Please describe.
Just cherrypick https://github.com/openshift/oadp-operator/commit/139f4f56281c55cfac6c66b930d6942e66dfb536
We are not going to add mutliarch images to prow/quay but deploy-olm for dev should be simple with cherrypick
Describe the solution you'd like
Describe alternatives you've considered
Additional context
Contributor guide
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
Start by reviewing commit 139f4f56281c55cfac6c66b930d6942e66dfb536 in the oadp-operator repository and compare its changes with the current branch. Apply the commit for the deploy-olm development workflow, then run the relevant deploy-olm validation to confirm the multiarch deployment configuration works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100