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

The 0.4.0 version of the Strimzi Kafka OAuth library for using OAuth authentication in Kafka clients and brokers has been released and should be available in the Maven repositories. The main

Hi, Release Candidate 1 of the 0.4.0 version of the Strimzi Kafka OAuth library is now available for testing: https://github.com/strimzi/strimzi-kafka-oauth/releases/tag/0.4.0-rc1. The main changes

Strimzi Kafka Operators 0.17.0 has been released. The main changes since 0.16 include: * Add possibility to set Java System Properties via CR yaml * Add support for Mirror Maker 2.0 * Add Jmxtrans

Release Candidate 4 of Strimzi Kafka Operators 0.17.0 is now available. There is only one additional fix since RC3: * Make sure the ZookeeperScaler does work will with custom CAs without the PKCS12

Release Candidate 3 of Strimzi Kafka Operators 0.17.0 is now available. There are some important fixes and improvements since RC2: * Fixed NPE which happen in KafkaRoller under rare circumstances *

Hi, segment.bytes uses the Java int type, which has a maximum possible value of 2147483647 (2^31-1). So although 10737418240 is a valid number it's too big. Kind regards, Tom

Hi, I am trying to apply custom segment.bytes value to kafka topic as follows. ---- apiVersion: kafka.strimzi.io/v1beta1 kind: KafkaTopic metadata: labels: strimzi.io/cluster: default name:

Yeah, the annotations are strings. So you need to wrap it into quotes to make it a string. Without them it will be interpreted as array.

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",

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

I'm afraid that is not possible. The Topic Operator is currently using Zookeeper for storing some additional data, so it it really needed there. Since Zookeeper will be removed from Kafka in the

Hi, For specifying the resources, you can do something like this: apiVersion: kafka.strimzi.io/v1alpha1 kind: KafkaConnect metadata: name: my-connect # ... spec: # ... resources:

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

Release Candidate 2 of Strimzi Kafka Operators 0.17.0 is now available. It took us more than two weeks since the RC1, but we spent them with a lot of testing and improving the code to make sure the