Does the new 0.17 operator uses kafka-connect 2.4.1 ? or still the 2.4.1 image?

Turns out the issue was the changed CRD had errors strimzi operator couldn't handle, following the logs of the operator pods, I've found the error and now it does update as expected.

Thanks, following your advice I've added: template: pod: metadata: annotations: ad.datadoghq.com/kafka-connect-container-name.logs: [{"type":"file", "source":"java","sourcecategory":"sourcecode", "ser

I've updated the crd after it created the deployment and pods and services (adding configs, annotations and resources)but it seems the deployment is stuck where I started Is there a way to update the

Thanks for the kind and authoritative response! I'll roll my own for now

Thanks I would try that! I was missing the pod/deployment sub level

Without zookeeper that is, I need topic operator without touching zookeeper

I want to use it for programmatic management of my topics, but my kafka is hosted in confluent and I don't think I can access the zookeeper cluster there

Trying to add pod annotations (for our log connector) and resource request/limits to the KafkaConnect created resources What should I add in the resource so it would create the pods/deployment with th

I've setup the most basic kafka persistent setup (see the crd below) But can't seem to understand how to run schema registy against it (with kafka based leader selection) I see kafka logs with endless

Turns out that adding ssl :{} in the spec. does the trick :)

For connection for my kafka instance (by eventhub kafka facade) I need the following properties security.protocol=SASL_SSL producer.sasl.mechanism=SASL_SSL consumer.sasl.mechanism=SASL_SSL I've verifi

I want to use strimzi to deploy debezium with kafka connect and eventhub kafka facade in my aks cluster, All the tutorial I've encountered are about using strimzi to create a kafka cluster (which I do