All binaries and tools used by any image are available and used with arm64 architecture ( might mainly apply to products )

[Maleware]

Just because a product or operator is building, doesn't mean the artefacts it contains are only arm64. On docker-desktop things usually work as intended since Qemu jumps in to help if a non-native binary needs execution.

Thus our artefacts need to be tested throughly on k3s or kind within a bare metal arm64 architecture.

This needs to be done:

• [ ] Testing operators if they run on bare arm64
  • [ ] https://github.com/stackabletech/kafka-operator/
  • [ ] https://github.com/stackabletech/hive-operator
  • [ ] https://github.com/stackabletech/secret-operator
  • [ ] https://github.com/stackabletech/nifi-operator
  • [ ] https://github.com/stackabletech/opa-operator
  • [ ] https://github.com/stackabletech/zookeeper-operator
  • [ ] https://github.com/stackabletech/trino-operator/
  • [ ] https://github.com/stackabletech/superset-operator
  • [ ] https://github.com/stackabletech/spark-k8s-operator
  • [ ] https://github.com/stackabletech/listener-operator
  • [ ] https://github.com/stackabletech/hdfs-operator
  • [ ] https://github.com/stackabletech/hbase-operator/
  • [ ] https://github.com/stackabletech/druid-operator
  • [ ] https://github.com/stackabletech/commons-operator
  • [ ] https://github.com/stackabletech/airflow-operator
• [ ] Testing product images if they run on bare arm64
  • [ ] https://github.com/stackabletech/docker-images/
• [ ] Fix problems

[Maleware]

I think once we have nightlies for arm64 running, we can omit this ticket.

[Maleware]

Done, since testing is enabled.