External-dns: Support armv7/8

Created on 4 Dec 2018 · 6Comments · Source: kubernetes-sigs/external-dns

Tried to build an arm64 version, tuns out that's not currently possible because:

Build dep uses https://raw.githubusercontent.com/golang/dep/master/install.sh which doesn't support arm.

There is also a pending issue here https://github.com/golang/dep/issues/1807 but it seems nobody cares.

Therefore could the build process altered so that it does not rely on that script?
Or is there a fundamental reason why this project wouldn't run on arm?

lifecyclrotten

Source

Xnyle

👍3

Most helpful comment

Sent in small PR to golang/dep to add arm and arm64 releases here: https://github.com/golang/dep/pull/2102
It's linked on that issue too.

kskewes on 11 Feb 2019

👍2

All 6 comments

There is no reason not to support arm64, but unfortunately I believe there are no plans to migrate to another dependency manager just yet. Ideally, we will use go modules in the future, but it's probably too early to jump on that.
We could, in the meantime, add a dedicated Makefile rule to build on arm, and we would be happy to review a PR that introduces such support.

Raffo on 5 Dec 2018

👍2

Sent in small PR to golang/dep to add arm and arm64 releases here: https://github.com/golang/dep/pull/2102
It's linked on that issue too.

kskewes on 11 Feb 2019

👍2

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

fejta-bot on 12 May 2019

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

fejta-bot on 11 Jun 2019

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

fejta-bot on 12 Jul 2019

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/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.