# I want to establish connectivity between filebeat running on a linux based VM and logstash running in kubernetes(logstash exposed through ingress)

**URL:** <https://discuss.elastic.co/t/i-want-to-establish-connectivity-between-filebeat-running-on-a-linux-based-vm-and-logstash-running-in-kubernetes-logstash-exposed-through-ingress/192781>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [July 29, 2019, 9:49pm UTC](https://discuss.elastic.co/t/i-want-to-establish-connectivity-between-filebeat-running-on-a-linux-based-vm-and-logstash-running-in-kubernetes-logstash-exposed-through-ingress/192781 "2019-07-29T21:49:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ntsh999](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ntsh999/32/51172_2.png) [@ntsh999](https://discuss.elastic.co/u/ntsh999)\
**Post date:** [July 29, 2019, 9:49pm UTC](https://discuss.elastic.co/t/i-want-to-establish-connectivity-between-filebeat-running-on-a-linux-based-vm-and-logstash-running-in-kubernetes-logstash-exposed-through-ingress/192781/1 "2019-07-29T21:49:54Z")

</div>

I have specified logstash output in the filebeat.yml file host: ["[https://example.com/logstash](https://example.com/logstash)"]. I have multiple services exposed through ingress and hence I want the logstash also to be exposed through the same ingress resource. The host attached to ingress resource is [https://www.example.com](https://www.example.com). And I am using the .crt file of the TLS/SSL certificate associated with [example.com](http://example.com) in the certificate autority key of the filebeat.yml to secure the connection between filebeat and logstash. And in the logstash.yml which is running on kubernetes I have specified the input as tcp type instead of beats type. Logstash service is running of ClusterIP Type and has the following ingress rule

```auto
   http:
     paths:
     - backend:
         serviceName: logstash-service
         servicePort: 5044
       path: /logstash

```

Now when I run this entire setup the filebeat on the VM gives me error

```auto
  output.go:100#011Failed to connect to backoff(async(tcp://https://example.com/logstash)): lookup https on 168.63.129.16:53: no such host
Jul 29 19:35:16 EIC-Development-IS filebeat[75346]: 2019-07-29T19:35:16.954Z#011INFO#011pipeline/output.go:93#011Attempting to reconnect to backoff(async(tcp://https://example.com/logstash)) with 7 reconnect attempt(s)
Jul 29 19:35:16 EIC-Development-IS filebeat[75346]: 2019-07-29T19:35:16.954Z#011DEBUG#011[logstash]#011logstash/async.go:111#011connect
Jul 29 19:35:16 EIC-Development-IS filebeat[75346]: 2019-07-29T19:35:16.957Z#011WARN#011transport/tcp.go:53#011DNS lookup failure "https": lookup https on 168.63.129.16:53: no such host

```

Is this setup technically possible? What should be the host what I should specify in filebeat and what should be the logstash input type? Will specifying the tls.crt specified in filebeat help in authenticating with /logstash?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [August 26, 2019, 9:50pm UTC](https://discuss.elastic.co/t/i-want-to-establish-connectivity-between-filebeat-running-on-a-linux-based-vm-and-logstash-running-in-kubernetes-logstash-exposed-through-ingress/192781/2 "2019-08-26T21:50:07Z")

</div>

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