Hi,

Just want to start of by saying, great project!

Also, I couldnt find the right place to raise this issue, so I am raising it here apologies.

Where I work we use debezium, in its kafka connect form and running in kubernetes, and it works ok.

That being said we find that kafka connect running on kubernetes isnt a great fit. The two scheduling systems overlap and interfere, and generally we find kafka connect a bad experience for the user (benthos / redpanda connect is much preferred for us).

I found the operator project for debezium, and my eyes lit up as it would improve this situation.

However, looking closer it seems like the operator for debezium is missing a few common configuration options that would allow us to adopt it, so I am enumerating them here in the hopes they could potentially get prioritized

• operator replicas arent configurable
• operator appears to not manage any kubernetes lease resources, so cannot run in a highly available fashion via leader election (hence replicas not configurable?)
• no way to configure kubernetes metadata via helm values (very common requirement)
• lack of ability to configure operators runtime in anyway via helm values e.g:
  • setting log verbosity
  • enabling structured logging

Again, great project. I will be following its progress

Thanks,
Max Sargent