RFC : Operator behaviour when a Topic is manually deleted from Kafka ? about koperator HOT 3 CLOSED

Just to add to the discussion - what should be the desired behavior when a cluster has topic deletion disabled and a KafkaCluster or KafkaTopic gets deleted? In the current state on master, if I am understanding sarama's documentation correctly, is that no error will be raised but the topic will remain in Kafka/Zookeeper. So an attempt to recreate the topic on a new or existing cluster using the same zookeeper will fail.

from koperator.

From Kubernetes perspective Kafka Topics and Users are external resources. In release 0.7.0 we removed the loop which periodically checked Kafka Topics. Since it is an external resource the operator will not receive any event in case of modification. I think this is the way to go.
It has some benefits like we don't need to implement an inner watcher logic for the Kafka resources.
Of course it has some drawbacks as well since if the user deletes a topic created through CR the operator will recreate it once an update happens on the related CR.

from koperator.

That's a fair move. Now we know how to handle such a situation. Thanks @baluchicken
Is this clearly stated in the docs ? (will check ASAP)
I think this can be closed then.

Thanks again for your great work

from koperator.