@she would it make sense to use Multiple docker-compose files.
My idea would be to change the docker-test structure to contain 1-3 docker-compose files with the same base structure of services (kafka,kcat,zookeeper,schemaregisty) with topics created corresponding to the use case and then individual files adding the concrete benchmark image.
This could then be composed and used like this:
docker-compose -f uc1-base.yaml -f uc1.kstreams.yaml up -d
From previous experience (in the Titan project), I can tell using multiple Docker-Compose files becomes really unhandy. I would say using a single Docker-Compose files for simple tasks is fine (although involving lots of copy-paste), but for any other case, Kubernetes resource files should be used. In fact, I already thought about dropping the Docker-Compose files entirely, but that would probably complicate things for new developers.