Philipp Moeller

We hit this issue after upgrading to postgres-operator 1.13.0 (which includes spilo `3.3-p1`). Any way to move this forward and get it merged?

Isn't this going to break `wal-e` because it still prints `name` in version `1.1.1`?

Looking at https://github.com/zalando/postgres-operator/blob/master/pkg/cluster/k8sres.go#L2524 I understand why the error is happening: the operator tries to "forward" the ownerReference set on the CR, but I don't understand why it is doing that...

@stianst Yes, I would very much prefer making it harder to run dev instances against production databases. Especially since users of the Keycloak Operator don't have immediate control over what...