# Connecting Enterprise Search and Kibana with ECK

**URL:** <https://discuss.elastic.co/t/connecting-enterprise-search-and-kibana-with-eck/284219>\
**Category:** Elastic Search\
**Created:** [September 14, 2021, 8:10pm UTC](https://discuss.elastic.co/t/connecting-enterprise-search-and-kibana-with-eck/284219 "2021-09-14T20:10:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![lgoolsby](https://avatars.discourse-cdn.com/v4/letter/l/90db22/32.png) [@lgoolsby](https://discuss.elastic.co/u/lgoolsby)\
**Post date:** [September 14, 2021, 8:10pm UTC](https://discuss.elastic.co/t/connecting-enterprise-search-and-kibana-with-eck/284219/1 "2021-09-14T20:10:58Z")

</div>

When connecting Kibana and Enterprise Search, [the docs](https://www.elastic.co/guide/en/enterprise-search/7.14/user-interfaces.html#user-interfaces-kibana-setup) say to use the host name. However, using the external DNS name that I configured for our k8s cluster does not work. I can change the host name to the internal IP address of the ES pod and the connection works.

How do configure Kibana to use the pod's name instead of IP?

```auto
apiVersion: kibana.k8s.elastic.co/v1
kind: Kibana
metadata:
  name: quickstart
  namespace: elastic-system
spec:
  version: 7.14.0
  count: 1
  elasticsearchRef:
    name: quickstart
  config:
    enterpriseSearch.host: http://10.x.x.x:3002
  http:
    tls:
      selfSignedCertificate:
        disabled: true

```

---

<div class="post-metadata">

**Author:** ![Rich\_Kuzsma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rich_kuzsma/32/66159_2.png) [@Rich\_Kuzsma](https://discuss.elastic.co/u/Rich_Kuzsma)\
**Post date:** [September 23, 2021, 2:48am UTC](https://discuss.elastic.co/t/connecting-enterprise-search-and-kibana-with-eck/284219/2 "2021-09-23T02:48:25Z")

</div>

Hello Lane,

You can connect to another pod using the service name plus `.default.svc`. With your configuration named `quickstart` you would set:  
`enterpriseSearch.host: https://quickstart-ent-http.default.svc:3002`

I found the service name for Enterprise Search, `ent-http`, by running `kubectl get svc`.

Here is a full Kubernetes YML that runs Elasticsearch, Kibana, and Enterprise Search, connected without the use of an IP. This YML uses the name `example` instead of `quickstart`:

```auto
apiVersion: elasticsearch.k8s.elastic.co/v1
kind: Elasticsearch
metadata:
  name: example
spec:
  version: 7.14.2
  nodeSets:
    - name: default
      count: 1
      config:
        # Not for production use, see: https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-virtual-memory.html
        node.store.allow_mmap: false
---
apiVersion: enterprisesearch.k8s.elastic.co/v1
kind: EnterpriseSearch
metadata:
  name: example
spec:
  version: 7.14.2
  count: 1
  elasticsearchRef:
    name: example
  config:
    kibana.external_url: https://localhost:5601
  podTemplate:
    spec:
      containers:
      - name: enterprise-search
        env:
        - name: JAVA_OPTS
          value: -Xms1500m -Xmx1500m
        resources:
          requests:
            memory: 2Gi
          limits:
            memory: 2Gi
---
apiVersion: kibana.k8s.elastic.co/v1
kind: Kibana
metadata:
  name: example
spec:
  version: 7.14.2
  config:
    enterpriseSearch.host: https://example-ent-http.default.svc:3002
  count: 1
  elasticsearchRef:
    name: example
  enterpriseSearchRef:
    name: example

```

Hope this helps!

---

<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:** [November 4, 2022, 8:32am UTC](https://discuss.elastic.co/t/connecting-enterprise-search-and-kibana-with-eck/284219/3 "2022-11-04T08:32:20Z")

</div>