mzi/strimzi-kafka-operator/issues/4676
>
> Thanks
>
> -Original Message-
> From: Vignesh
> Sent: 16 June 2025 01:34
> To: users@kafka.apache.org
> Subject: Re: Kafka Connect on Kubernetes: Statefulset vs Deployment
>
> [You don't often get email from
mziPodSet some time ago because of this
issue.
https://github.com/strimzi/strimzi-kafka-operator/pull/8090
https://github.com/strimzi/strimzi-kafka-operator/issues/4676
Thanks
-Original Message-
From: Vignesh
Sent: 16 June 2025 01:34
To: users@kafka.apache.org
Subject: Re: Ka
Kafka Connect is a stateless component by design. It relies on external
Kafka topics to persist its state, including connector configurations,
offsets, and status updates. In a distributed Kafka Connect cluster, this
state is managed through the following configurable topics:
-
config.stora
I created the docker+kube stuff for our kafka-connect at my current job.
I use standard deployment. kafka-connect doesn't care of hostname or IP.
The sole trick is to inject the connector configuration at runtime (if you
want).
--
Raph
On 14/06/2025 2:12 pm, Prateek Kohli wrote:
> Hi All,
>
>
something wrong?
From: Federico Valeri
Sent: Saturday, June 14, 2025 7:33:29 PM
To: users@kafka.apache.org
Subject: Re: Kafka Connect on Kubernetes: Statefulset vs Deployment
[You don't often get email from fedeval...@gmail.com. Learn why this is
importa
Hi Prateek.
In a Kafka Connect cluster, the advertised address represents the
identity of the worker node. Connectors and tasks are scheduled to the
individual worker nodes based on their identity.
If you use a Kubernetes Deployment, when you roll the cluster, new
Pods with new IPs will be be cre
