Hi Maros, thanks for the KIP.

FV0: One of the major benefits here is the possibility to thoroughly test
the official Docker images that users actually deploy. I would make this
more prominent in the motivation section.

FV1: The proposal states "the compression test went from ~85s to ~12s." Can
you add the exact test name and relevant details about the test hardware?
How can someone try this test locally to reproduce the comparison?

FV2: "Network partitions, latency and bandwidth limits; log directory
failures." Ducktape implements network faults through iptables rules over
SSH, which is clunky but well understood. How does the container approach
implement network partitions, latency injection, and bandwidth constraints?
Would this also make Trogodor redundant?  If so, it would be worth stating
explicitly. A minimal example for both network partition and log directory
failure would make the proposal much more concrete.

FV3: Ducktape collects logs from every node into a structured results
directory, organized by test, service, and node, and these artifacts are
essential for debugging failures, especially in CI. Does the new suite
provide anything equivalent? A concrete example of the results layout would
help.

FV4: "Replace Ducktape entirely: not possible for compatibility coverage of
releases older than 4.0, such as 2.x clients." Can you expand on this? Is
this an inherent limitation of the Testcontainers approach (no Docker
images for older releases), a consequence of the KRaft-only design, or
something else? Maintaining two entirely different system test frameworks
indefinitely is not viable IMO.

FV5: The proposal is thin on the ClusterInstance API surface. What does
that object expose? Can it return individual broker containers for targeted
fault injection? Can it expose JMX metrics? Can it wait for partition
reassignment to complete? The existing Ducktape services have rich APIs
(await_no_under_replicated_partitions(), controller(), signal_node()) built
up over years.

Cheers
Fede


On Thu, Nov 12, 2026 at 1:38 PM Maroš Orsák <[email protected]>
wrote:

> Hello,
>
> I would like to start a discussion on KIP-1393. All details in the KIP:
>
> https://cwiki.apache.org/confluence/spaces/KAFKA/pages/462816417/KIP-1393+Container-based+system+tests+with+JUnit+and+Testcontainers
> <
> https://cwiki.apache.org/confluence/spaces/KAFKA/pages/462816417/KIP-1393+Container-based+system+tests+with+JUnit+and+Testcontainers
> >
>
> Related discussion to this topic:
> https://lists.apache.org/thread.html/t7o4c1nxvx4bpf7387f07hmqj7fcqgbh.
>
> Cheers,
>
> Marios
>

Reply via email to