couldn't find arm64 image for kanister

[ashiq-betaflux]

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Environment
Kubernetes Version/Provider: ...
Storage Provider: ...
Cluster Size (#nodes): ...
Data Size: ...

Additional context
Add any other context or screenshots about the feature request here.

[github-actions]

Thanks for opening this issue 👍. The team will review it shortly.

If this is a bug report, make sure to include clear instructions how on to reproduce the problem with minimal reproducible examples, where possible. If this is a security report, please review our security policy as outlined in SECURITY.md.

If you haven't already, please take a moment to review our project's Code of Conduct document.

[pavannd1]

Hi @ashiq-betaflux, thanks for opening this issue! We have ARM support in our roadmap and will be addressed in the near future. Please let me know if you are interested in contributing to it.

[ashiq-betaflux]

yes, iam interested. i will work on.

[haimgel]

Hey @ashiq-betaflux, is this something you are still working on? I'm also interested in this feature.

[ashiq-betaflux]

@haimgel No..!, i got some other alternative ideas, so i left it there

[github-actions]

This issue is marked as stale due to inactivity. Add a new comment to reactivate it.

[XBeg9]

Same here, I was unable to find the arm64 image for kanister, am I missing something or it's still in development?

[mocdaniel]

What's the blocker for this to happen? I just started looking into Kanister and haven't gotten to the implementation details yet, but isn't it 'just' a Kubernetes controller acting on some CRDs?
If anything, I'd expect some specific Blueprints or actions/tasks run in specific other pods/containers to not work on ARM, but not the controller itself.

[viveksinghggits]

There is no blocker @mocdaniel .
The problem is if the controller docker image is built using goreleaser from an arm based machine the container image will be built for the arm platform. And if we deploy that on a k8s cluster (linux/amd64), the pod would not work properly.
Apart from that, the kanctl binary that is built right now and published is for amd64 machines, so if someone wants to use kanctl on the arm machines they will have to build the binary themselves.
These are the two problems that I am planning to fix as part of #3015.

[github-actions]

This issue is marked as stale due to inactivity. Add a new comment to reactivate it. CC @kanisterio/maintainers

[github-actions]

This issue is closed due to inactivity. Feel free to reopen it, if it's still relevant. CC @kanisterio/maintainers

[viveksinghggits]

We need to take this up.