You don't need to write any unless your fixing bugs or contributing to the project (I'd say parent's comment still stands though).

> I'd say parent's comment still stands though

That people will appreciate Go because a tool is written in it? I'm dubious.

I use Kafka on a daily basis and read its source code with regularity to better understand its behaviour. and while I love what Kafka can handle, and how resilient it is, it doesn't enamour me more, or less, of Scala. What I love about Kafka has little to do with the language and everything to do with the architecture and design of the system.

Go is probably more readable than a lot of the legacy Scala in Kafka admittedly (although their new Scala and Java code is far more readable) which I guess could convince people to give it a try.

Well, maybe you have to write third party controller(or operator) for k8s. That was actually a case for me, recently