v1.37.0 arm64 image exits 132 (SIGILL) on Raspberry Pi 4 Cortex-A72

**Describe the bug**

The official `docker.dragonflydb.io/dragonflydb/dragonfly:v1.37.0` arm64 image pulls and is scheduled successfully on a Raspberry Pi 4 Model B k3s worker, but the Dragonfly container exits immediately with code 132 and emits no application log. On Linux, exit 132 is `SIGILL`.

This appears related to the ARM ISA baseline of the published image. The Cortex-A72 worker reports only:

```text
fp asimd evtstrm crc32 cpuid
```

In particular, it does not report ARM Large System Extensions (LSE) atomics. This is a current-version data point for the older open ARM report in #2479.

**To Reproduce**

1. Use a Raspberry Pi 4 Model B with a Cortex-A72 CPU, running 64-bit Ubuntu Linux and k3s.
2. Install Dragonfly Operator `v1.5.0`.
3. Apply a `Dragonfly` resource with the official image `docker.dragonflydb.io/dragonflydb/dragonfly:v1.37.0`, one or more replicas, and ordinary Redis port/snapshot PVC configuration.
4. Inspect the Dragonfly pod after it starts.
5. Observe `CrashLoopBackOff`; the last container state is `Error` with exit code `132`, and `kubectl logs` is empty.

The image pull, PVC provisioning, pod scheduling, secret injection, and operator reconciliation all complete before the process exits.

**Expected behavior**

Either:

- the official arm64 image starts on the Raspberry Pi 4 Cortex-A72, or
- the published image/documentation clearly states the required ARM ISA baseline and the process emits an actionable startup diagnostic instead of failing silently with `SIGILL`.

An `armv8-a` generic or Cortex-A72-compatible image variant would make the supported compatibility boundary explicit.

**Screenshots**

Not applicable.

**Environment (please complete the following information):**

- OS: Ubuntu 26.04 LTS
- Kernel: `Linux pleiades-4 7.0.0-1014-raspi #14-Ubuntu SMP PREEMPT_DYNAMIC Mon Jun 29 20:10:16 UTC 2026 aarch64 GNU/Linux`
- Containerized?: Kubernetes (k3s, containerd `2.3.2-k3s2`)
- Dragonfly Version: `v1.37.0`
- Image: `docker.dragonflydb.io/dragonflydb/dragonfly:v1.37.0`
- Resolved image digest: `sha256:84b1009aee0b68327758bce8e99ed514f782d713353acc46caf5738feaa481d6`
- Hardware: Raspberry Pi 4 Model B Rev 1.4, Cortex-A72, arm64
- CPU features: `fp asimd evtstrm crc32 cpuid`
- Dragonfly Operator: `v1.5.0`

**Reproducible Code Snippet**

```yaml
apiVersion: dragonflydb.io/v1alpha1
kind: Dragonfly
metadata:
name: dragonfly
spec:
image: docker.dragonflydb.io/dragonflydb/dragonfly:v1.37.0
replicas: 1
args:
- --dbnum=4
```

The relevant observed container state is:

```text
Last State:
Terminated:
Reason: Error
Exit Code: 132
```

`kubectl logs ` returns no output.

**Additional context**

As a bounded local compatibility experiment, we are building the same tag natively with `-march=armv8-a -mtune=cortex-a72 -mno-outline-atomics`. That is not intended as a fork. It is only a way to validate that the failure is the published image's ISA baseline and to determine whether a generic arm64 build can serve this hardware.

Please confirm the intended minimum ARM baseline for current official images and whether a generic `armv8-a`/Cortex-A72 variant is feasible. If Raspberry Pi 4 is intentionally unsupported, documenting that prominently would also resolve the ambiguity.

No source file or test is named. Start by reproducing the failure with the v1.37.0 image on a Raspberry Pi 4 Cortex-A72 and inspect the published image's ARM ISA baseline; done means confirming the minimum supported baseline and either providing a compatible image variant or documenting the boundary and startup behavior.

Written by the indexing model from the issue text.