Is your feature request related to a problem? Please describe.
I tried running the operator in my k8s cluster at home, it works great, until one time it got restarted (for de-scheduler, expected restart) and noticed the
exec /manager: exec format error
This is almost certainly an indication that the operator is not ARM64 compatible. Would be great to have it compatilbe with ARM64.
I am running docker.dragonflydb.io/dragonflydb/operator:v0.0.9 which is what I got from the yaml in the docs (when installing the operator) few days ago.
Describe the solution you'd like
An image that is compatible with both ARM64 and AMD64
Describe alternatives you've considered
Modify the operator yaml to have a nodeSelector to only select amd64 machines to run on.
Additional context
I think in the future, ARM64 and AMD64 clusters will be more common, they are already common so I think this feature is a worthy investment of time.
Is your feature request related to a problem? Please describe. I tried running the operator in my k8s cluster at home, it works great, until one time it got restarted (for de-scheduler, expected restart) and noticed the
This is almost certainly an indication that the operator is not ARM64 compatible. Would be great to have it compatilbe with ARM64.
I am running
docker.dragonflydb.io/dragonflydb/operator:v0.0.9
which is what I got from the yaml in the docs (when installing the operator) few days ago. Describe the solution you'd like An image that is compatible with both ARM64 and AMD64Describe alternatives you've considered Modify the operator yaml to have a nodeSelector to only select amd64 machines to run on.
Additional context I think in the future, ARM64 and AMD64 clusters will be more common, they are already common so I think this feature is a worthy investment of time.