unable to start new cluster with existing persistent volumes

After deleting a cluster by running `kubectl delete -f example.yaml`, and _not_ deleting PVCs and PVs, I start a new cluster with `kubectl apply -f example.yaml`. The pod `cockroachdb-0` remains unready with no other pods creating:

```
cockroachdb-0 0/1 Running 0 2m17s
```

The pod shows:

```
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 2m23s default-scheduler Successfully assigned default/cockroachdb-0 to gke-cockroachdb-default-pool-01b609ce-vkqv
Normal SuccessfulAttachVolume 2m17s attachdetach-controller AttachVolume.Attach succeeded for volume "pvc-2c986ce6-96b8-42bf-80c9-10d4e39ace2c"
Normal Pulled 2m14s kubelet, gke-cockroachdb-default-pool-01b609ce-vkqv Container image "cockroachdb/cockroach:v20.2.8" already present on machine
Normal Created 2m14s kubelet, gke-cockroachdb-default-pool-01b609ce-vkqv Created container db
Normal Started 2m14s kubelet, gke-cockroachdb-default-pool-01b609ce-vkqv Started container db
Warning Unhealthy 15s (x22 over 2m) kubelet, gke-cockroachdb-default-pool-01b609ce-vkqv Readiness probe failed: HTTP probe failed with statuscode: 500
```

I'm only able to create the new cluster if I first delete the volumes with `kubectl delete pv,pvc --all`.

This is using the Operator version currently at https://github.com/cockroachdb/cockroach-operator/blob/master/manifests/operator.yaml on GKE and CRDB v20.2.8.