Skip to content

[Kafka] Ability to set a prefix for Transactional ID #3600

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
brunodomenici opened this issue May 16, 2025 · 0 comments
Open

[Kafka] Ability to set a prefix for Transactional ID #3600

brunodomenici opened this issue May 16, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@brunodomenici
Copy link

Is your feature request related to a problem? Please describe.

Today we need to give permissions for managing transactions in Kafka with the pod name of the sensor, which could lead to collisions in a mutualized Kafka environments.
Image 2 different teams working in separated namespaces with the same sensor name using the same Kafka instances with different Kafka credentials. We need to give:

User:user1,TransactionalId,PREFIXED,pod-name-,Write,Allow,*
User:user2,TransactionalId,PREFIXED,pod-name-,Write,Allow,*

I know the pod name will have the suffix of the ReplicaSet hash, but in the Kafka side we have 2 users who can potentially manage the same transaction id.

Describe the solution you'd like

Ability to configure a prefix for this, like commented in #2654 (comment) would fix the issue.

Describe alternatives you've considered

Give the same Kafka permissions for all users.

Additional context

This is the same of #2654 but it's closed, so I decided to create a new one.


Message from the maintainers:

If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.

@brunodomenici brunodomenici added the enhancement New feature or request label May 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant