Running Apache Kafka on Kubernetes can be beneficial in certain situations for large traditional enterprise companies, despite the complexity it introduces. It becomes the organizational path of least resistance when most applications are already running on Kubernetes, and deploying Kafka outside of Kubernetes can cause significant organizational headaches. However, successful deployment requires cooperation from skilled storage and network teams to manage shared storage devices and handle message routing to specific brokers. It is recommended against choosing Kafka as the first service to run on Kubernetes, but rather as part of a broader application ecosystem where all applications are managed with Kubernetes. With tools like Helm Charts and Confluent Operator, running Kafka on Kubernetes can be easier than other methods and offers consistent low latency when storage and network teams understand the requirements.