You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
@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?
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.
The text was updated successfully, but these errors were encountered: