It's a common practice in Kubernetes resources to expose a replicas property in the spec that controls how many pods should be started.

Given that we do not support more than 1 pod for a DebeziumServer resource, we should treat this much like we do with Kafka Connect's tasks.max property where it would be either 0 or 1.

So rather than

apiVersion: debezium.io/v1alpha1
metadata:
  name: my-debezium-server
  annotations:
    debezium.io/stop: true

we'd follow the best practice and do

apiVersion: debezium.io/v1alpha1
metadata:
  name: my-debezium-server
spec:
  replicas: 0

Sourced from https://debezium.zulipchat.com/#narrow/channel/392460-community-operator/topic/Best.20way.20to.20stop.20Debezium.20when.20using.20operator.20to.20reset.20offse/with/546583997