ELK as a service without beats in Kubernetes

I want to build ELK as a service in kubernetes.
How to configure logstash to handle external syslog data into the ELK stack in kubernetes?
Can I do it without using beats?
Anyone can help?

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.