# ECK Expose Kibana Service

**URL:** <https://discuss.elastic.co/t/eck-expose-kibana-service/286215>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Tags:** docker\
**Created:** [October 8, 2021, 9:32am UTC](https://discuss.elastic.co/t/eck-expose-kibana-service/286215 "2021-10-08T09:32:33Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Adriann](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adriann/32/77780_2.png) [@Adriann](https://discuss.elastic.co/u/Adriann)\
**Post date:** [October 8, 2021, 9:32am UTC](https://discuss.elastic.co/t/eck-expose-kibana-service/286215/1 "2021-10-08T09:32:33Z")

</div>

Hello,

I am building ELK Stack solutions using ECK and minikube. The working solution will be uploaded to GCK. I am able to connect to kibana after I do this command from documentation  
`kubectl port-forward service/quickstart-kb-http 5601`  
But this solution is temporary because works only if the command is run in the console.

How Can I permanently "expose" kibana services to be available on specific IP and DNS name?

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [October 11, 2021, 3:18am UTC](https://discuss.elastic.co/t/eck-expose-kibana-service/286215/2 "2021-10-11T03:18:35Z")

</div>

Perhaps you need an ingress controller if you mean you are goin to deploy on GKE (not sure what GCK is)

Here is a post I wrote on that.

> [@Is Kibana supported on GKE through default google ingress ? doesn't seem so](https://discuss.elastic.co/t/is-kibana-supported-on-gke-through-default-google-ingress-doesnt-seem-so/264067/14):
>
> Apologies I have had some other items on my plate. Remember I did this via ECK not Helm, I am an expert in neither, but I did this all very vanilla. So basically following at the steps above here is what I deployed. I did notice sometimes seems like perhaps there is a race condition or something so I deployed the elasticsearch and kibana separate and let it all come up first. Then I applied the the ingress so. kubectl -f es-kb.yml # elasticsearch kibana deploy with ECK apiVersion: elasticse…

---

<div class="post-metadata">

**Author:** ![Adriann](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adriann/32/77780_2.png) [@Adriann](https://discuss.elastic.co/u/Adriann)\
**Post date:** [October 12, 2021, 1:32pm UTC](https://discuss.elastic.co/t/eck-expose-kibana-service/286215/3 "2021-10-12T13:32:24Z")

</div>

The problem was in my minor understanding of Kubernetes services' architecture. Thank you for your help 🙂

---

<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 9, 2021, 1:32pm UTC](https://discuss.elastic.co/t/eck-expose-kibana-service/286215/4 "2021-11-09T13:32:48Z")

</div>

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