Does anyone know why the spicedb operator might be making two spicedb clusters? My k8s config is this:

apiVersion: v1
kind: Namespace
metadata:
  labels:
    kubernetes.io/metadata.name: spicedb
  name: spicedb
---
apiVersion: authzed.com/v1alpha1
kind: SpiceDBCluster
metadata:
  name: spicedb-cluster
  namespace: spicedb
spec:
  config:
    image: authzed/spicedb:v1.35.2
    datastoreEngine: postgres
  secretName: spicedb-config
---
apiVersion: v1
kind: Secret
metadata:
  name: spicedb-config
  namespace: spicedb
stringData:
  preshared_key: 'my-key' // redacted
  datastore_uri: 'my-uri' // redacted

And I'm applying it like this:

kubectl apply --server-side -f https://github.com/authzed/spicedb-operator/releases/download/v1.16.1/bundle.yaml
kubectl apply -f ./my-file.yaml

Resulting in these pods after migration completes:

spicedb-operator   spicedb-operator-5c449f879-x78fr                       1/1     Running   0          4m12s
spicedb            spicedb-cluster-spicedb-857f5f6b84-6qskn               1/1     Running   0          3m46s
spicedb            spicedb-cluster-spicedb-857f5f6b84-ph565               1/1     Running   0          3m46s