Skip to content
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

Move Connect / MM2 configuration preparation from the shell scripts to the operator #10668

Open
scholzj opened this issue Oct 2, 2024 · 3 comments

Comments

@scholzj
Copy link
Member

scholzj commented Oct 2, 2024

Some time ago, we changed the way how we generate the configuration for Kafka brokers (and controllers) from it being done inside bash scripts in the container to have it done in the operator and share it via Config Map / Secret to the Pods which do only minimal changes to it (ideally none as #10656 tries to achieve). This leads to reduced footprint in the container image, improved test coverage (as the bash scripts are currently only tested in STs and have no unit tests).

I think this was a good change and we should try to continue in this direction with other operands - in particular Connect / MM2 next.

@ppatierno
Copy link
Member

Triaged 03.10.2024: agreed on implementing this.

@varada-sunanda-ibm
Copy link
Contributor

@scholzj I’m interested in contributing more to Strimzi and would love to be involved in development. Is this something I can pick up as the next candidate?

@scholzj
Copy link
Member Author

scholzj commented Oct 21, 2024

I guess you can if you want. But this is a fairly advanced issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants