Bug report

Debezium Operator defaults to RollingUpdate. However, until we have a locking mechanism in place - it is not a safe default. It can lead to out of order events and with our connector (mysql) in particular - issues with conflicting server ids.

What Debezium connector do you use and what version?

mysql - 3.0.0-SNAPSHOT

What is the connector configuration?

N/A

What is the captured database version and mode of deployment?

N/A

What behavior do you expect?

For now, until we have a good locking mechanism for writes, we should default to `Recreate`.

What behavior do you see?

The current strategy is the default `RollingUpdate` which isn't mechanically safe.

Do you see the same behaviour using the latest released Debezium version?

Yes

Do you have the connector logs, ideally from start till finish?

N/A

How to reproduce the issue using our tutorial deployment?

N/A