ARM version

[nlamirault]

Is a multi-architecture version (ARM) possible?

[fejta-bot]

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.

Prevent issues from auto-closing with an /lifecycle frozen comment.

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]

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
/remove-lifecycle stale

[fejta-bot]

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

[nvtkaszpir]

/reopen

[k8s-ci-robot]

@nvtkaszpir: Reopened this issue.

In response to this:

/reopen

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.

[nvtkaszpir]

Reopening due to the fact that more and more hardware is used nowadays and maybe it is a good time to reconsider it.

[nvtkaszpir]

/remove-lifecycle rotten

[nvtkaszpir]

/assign @Random-Liu
Maybe it is worth to add multi-arch builds?
Should it be then converted to new issue?

[fejta-bot]

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

[povilasv]

/remove-lifecycle stale

[fejta-bot]

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

[cerebrate]

/remove-lifecycle stale

I have several ARM-based clusters that could use this.

[fejta-bot]

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

[cerebrate]

/remove-lifecycle stale

Still relevant.

[invidian]

Lokomotive would be also interested in ARM version (kinvolk/lokomotive#1384).

[fejta-bot]

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-contributor-experience at kubernetes/community.
/lifecycle stale

[invidian]

/remove-lifecycle stale

[vteratipally]

NPD started releasing arm versions from v0.8.8

[nvtkaszpir]

@vteratipally on release page of v0.8.8 (as of page of writing) there are only linux-amd64 and windows builds.
So where is ARM version?
Should I just run make with my own toolchain cause it's not in CI?

[vteratipally]

I apologize for the confusion, the NPD arm binaries would be released from the next version.

[vteratipally]

https://github.com/kubernetes/node-problem-detector/releases/tag/v0.8.9

[nvtkaszpir]

thx, very nice!

[cerebrate]

Thanks, working great for me!