Kroxy has its own release pipelines for the releases - https://master-jenkins-csb-amq-streams.apps.ocp-c1.prod.psi.redhat.com/job/downstream/job/kroxy/

It is needed to provide some kind of manual trigger (as we have for Strimzi and Console) for running the jobs without need of copying all the stuff to all the jobs.

There is currently no plan to create some "uber" trigger (but can be in few months) that will start all jobs for all components for the streams for Apache Kafka release - respectively, it's on the component owner (Strimzi/Kroxy/Console) to run the tests in case that there is new CR that influences their component - which every component owner should check and determine if the jobs should be triggered or not. Even if that makes sense to have everything automated, everyone should really check whether all the values, images, and changes are correct for particular component and CR.

That's why we have just "manual trigger" and not some "automatic trigger" which would do everything.