# Exposing Kibana behind GKE ingress (UNHEALTHY state)

**URL:** <https://discuss.elastic.co/t/exposing-kibana-behind-gke-ingress-unhealthy-state/267684>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [March 18, 2021, 2:44pm UTC](https://discuss.elastic.co/t/exposing-kibana-behind-gke-ingress-unhealthy-state/267684 "2021-03-18T14:44:09Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![lmes3oud](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lmes3oud/32/85735_2.png) [@lmes3oud](https://discuss.elastic.co/u/lmes3oud)\
**Post date:** [March 22, 2021, 3:49pm UTC](https://discuss.elastic.co/t/exposing-kibana-behind-gke-ingress-unhealthy-state/267684/5 "2021-03-22T15:49:22Z")

</div>

Hi @charith-elastic, thank you very much, this is really helpful.  
I will create a [topic](https://discuss.elastic.co/t/expose-kibana-behind-a-subpath-using-gce-ingress/267987) about it and accept the solutions for more visibility.

---

_[View the full topic](https://discuss.elastic.co/t/exposing-kibana-behind-gke-ingress-unhealthy-state/267684)._