workload-cluster-operator controlleer OOM'ing

I see this in my development environment:

k get pods -n workload-cluster-operator-system                                                             
NAME                                                           READY   STATUS             RESTARTS         AGE
workload-cluster-operator-controller-manager-c8df787d6-chd2p   1/2     CrashLoopBackOff   232 (107s ago)   20h

  - containerID: containerd://deae61a224303eda4e12f513710526bcce7bad848aae31d8d5414fd193be0d8e
    image: registry.gitlab.com/sylva-projects/sylva-elements/workload-cluster-operator:v0.4.0
...
    lastState:
      terminated:
        containerID: containerd://deae61a224303eda4e12f513710526bcce7bad848aae31d8d5414fd193be0d8e
        exitCode: 137
        finishedAt: "2025-06-19T08:35:47Z"
        reason: OOMKilled
                ^^^^^^^^
        startedAt: "2025-06-19T08:35:29Z"
    name: manager
    ready: false
    restartCount: 232
    started: false
    state:
      waiting:
        message: back-off 5m0s restarting failed container=manager pod=workload-cluster-operator-controller-manager-c8df787d6-chd2p_workload-cluster-operator-system(907f5f86-892c-4891-a25d-fbfed64a9c1f)
        reason: CrashLoopBackOff

(my setup has default settings with memory limit set to 128Mi)