[Call Summary] Community Call - April 9th 2026

[Robert Young]

Key points and actions from today’s community call:

## AI Contribution Policy
We are looking at how to move this forward. There are still open questions on the PR, so we are waiting for replies before we merge.
https://github.com/kroxylicious/.github/pull/27

## Strimzi v1 Resources
Keith highlighted a new proposal around Kroxylicious Operator integration with Strimzi. We discussed whether to break backwards compatibility to jump to supporting v1 Strimzi resources immediately, versus supporting some more complex compatibility strategy. The general feeling is that the existing feature is currently too embryonic and undocumented to be usable as-is. So we favour breaking compatibility rather than implementing a more complex solution. Please add any further ideas to the issue.
https://github.com/kroxylicious/design/pull/92

## Supporting Topics in the Entity Isolation Filter.
This issue represents a significant amount of work. We discussed breaking it down to deliver minimal Topic isolation, possibly deferring regex support. There is some hesitation regarding its priority, as it is difficult to assess value without more user feedback. Tom suggested we could pause and wait for User feedback, but noted the feature isn't compelling without topic isolation. While we considered avoiding topic IDs to save time, Keith noted this would require downgrading the protocol versions a lot, so was for including Topic ID support immediately to avoid these risks. A separate analysis is needed to see how we can best phase this.
https://github.com/kroxylicious/kroxylicious/issues/3504

## Correlated Request/Response API
The group concurred that this API is worth adding, so we will move forward with a design proposal. Tom also noted that due to recent ApiVersions manipulation, we should also look into allowing Filters to declare their supported versions.
https://github.com/kroxylicious/design/pull/93

## TLS Configuration Class Reuse
We discussed issues with TLS class reuse. Extending TLS options currently requires implementation across all usages of the shared config classes, or selectively rejecting parts of the new config. We are supportive of making changes here to improve how we handle these extensions, so Tom will create a design proposal.
https://github.com/kroxylicious/design/pull/94

Thanks,
Rob Young