Bug 2035899
| Summary: | Operator-sdk run bundle doesn't support arm64 env | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Fan Jia <jfan> |
| Component: | Operator SDK | Assignee: | Jesus M. Rodriguez <jesusr> |
| Status: | CLOSED ERRATA | QA Contact: | Fan Jia <jfan> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.10 | CC: | aos-bugs, jlanford, psundara |
| Target Milestone: | --- | Flags: | jesusr:
needinfo-
|
| Target Release: | 4.11.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: |
Feature:
Allow building arm64 operators
Reason:
Support arm64 architecture
Result:
Operator-sdk now supports building operator images targeted at arm64.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-08-10 10:41:05 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Comment 1
Prashanth Sundararaman
2022-01-04 16:06:53 UTC
I was right in comment #3, opm did not yet support arm64 until release 1.20. The scenario is that we try to download opm and there was no arm64 opm until release 1.20. * see release 1.20 has arm64 binaries: https://github.com/operator-framework/operator-registry/releases/tag/v1.20.0 * see that prior to 1.20 there were no arm64 binaries: https://github.com/operator-framework/operator-registry/releases/tag/v1.19.5 moving this bug to 4.11 when we can better support arm64 . operator-sdk v1.19.0 upstream will have the newer opm, then we can revisit arm64 across the board. opm:latest support arm64 now. verified. run bundle success in arm cluster. operator-sdk version: "v1.18.1-ocp", commit: "1d8c39dd75680daaf911c10582cf755c5f16da5b", kubernetes version: "v1.22", go version: "go1.17.4", GOOS: "linux", GOARCH: "amd64" operator-sdk run bundle quay.io/olmqe/xxxxx-bundle:V4.10 INFO[0060] Successfully created registry pod: quay-io-olmqe-xxxxx-bundle-v4-10 INFO[0061] Created CatalogSource: xxxxx-catalog INFO[0061] OperatorGroup "operator-sdk-og" created INFO[0062] Created Subscription: xxxxx-v0-0-1-sub INFO[0073] Approved InstallPlan install-4j2ch for the Subscription: xxxxx-v0-0-1-sub INFO[0073] Waiting for ClusterServiceVersion "default/xxxxx.v0.0.1" to reach 'Succeeded' phase INFO[0073] Waiting for ClusterServiceVersion "default/xxxxx.v0.0.1" to appear INFO[0085] Found ClusterServiceVersion "default/xxxxx.v0.0.1" phase: Pending INFO[0087] Found ClusterServiceVersion "default/xxxxx.v0.0.1" phase: Installing INFO[0117] Found ClusterServiceVersion "default/xxxxx.v0.0.1" phase: Succeeded INFO[0117] OLM has successfully installed "xxxxx.v0.0.1" Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:5069 |