Operator-sdk: Add operator-sdk support to aarch64 architecture

[ssbano]

Feature Request

Add operator-sdk support to aarch64 architecture

[hasbro17]

@ssbano Do you mean supporting arm64 binaries?

Just a heads up that this is not on our immediate roadmap.
https://github.com/operator-framework/operator-sdk/blob/master/doc/dev/release.md#operating-systems-and-architectures

Community PRs are always welcome though.
You will need to add arm64 support for the SDK binary and the Helm/Ansible base images similar to how it was added for ppc64le https://github.com/operator-framework/operator-sdk/pull/1533

Although I should point out that even ppc64le isn't complete since the ansible-operator base images aren't multi arch yet.

[ssbano]

@hasbro17

Yeah... arm64v7|8/aarch64

I can create the build to (SDK/Ansible) engine

Best Regards,
Fabio Sbano

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[fr34k8]

no progress here ? @ssbano @hasbro17

[estroz]

@ssbano @fr34k8 this isn't necessarily a high priority issue, but we'd welcome a PR. See the reference PR in the comment above: https://github.com/operator-framework/operator-sdk/issues/1996#issuecomment-536783478.

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci-robot]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[estroz]

@ssbano @fr34k8 we recently added arm64 support: #2742

[geerlingguy]

I'm assuming standard arm/armv7 is not on the roadmap, though? I just thought about using some of my operators built with Ansible to a Pi cluster... and realized that I can't get any of them to start because of:

root@turing-master:/home/pirate# kubectl logs drupal-operator-7f4b5dcdcb-xb5s6 -c ansible
standard_init_linux.go:211: exec user process caused "exec format error"
root@turing-master:/home/pirate# kubectl logs drupal-operator-7f4b5dcdcb-xb5s6 -c operator
standard_init_linux.go:211: exec user process caused "exec format error"

[agaffney]

@geerlingguy That exec format error message is probably due to #3233. I noted a workaround in that issue.