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

I used the open source helm chart from Confluent: https://github.com/confluentinc/cp-helm-charts/tree/v5.4.0/charts/cp-schema-registry The heap settings and resource limits were not sufficient for the

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

The Release Candidate 1 of Strimzi Kafka Operators 0.17.0 is now available. It doesn't include many new features, but some of those included were in high demand. The main features are: * Add

Strimzi Kafka Bridge 0.15.2 is now available with the following changes: * Fixed missing Jackson Core dependency For more details go to:

Strimzi Kafka Bridge 0.15.1 is now available with the following changes: * Bumped Apache Kafka version to 2.4.0 and other dependencies For more details go to:

The 0.3.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

Strimzi Kafka Operators 0.16.2 is now available with two bug fixes: * Fix bug in upgrade when the Kafka.spec.kafka.version field is not specified * Fix network policies for port 3.11 on older

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

Strimzi Kafka Operators 0.16.1 patch release is now available. The main changes since 0.16.0 include: Fix connector operator when Kafka Connect runs in a different namespace For more details go to:

Strimzi Kafka Operators 0.16.0 is now available with a lot of great new features. The main changes since 0.15.0 include: * Add support for Kafka 2.4.0 and upgrade from Zookeeper 3.4.x to 3.5.x * Drop

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