# Kibana ingress not working after upgrading to eck 1.1.0 **URL:** \ **Category:** Elastic Cloud on Kubernetes (ECK)\ **Created:** [May 12, 2020, 8:26pm UTC](https://discuss.elastic.co/t/kibana-ingress-not-working-after-upgrading-to-eck-1-1-0/232316 "2020-05-12T20:26:13Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![aman26ps](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aman26ps/32/82604_2.png) [@aman26ps](https://discuss.elastic.co/u/aman26ps)\ **Post date:** [May 12, 2020, 8:26pm UTC](https://discuss.elastic.co/t/kibana-ingress-not-working-after-upgrading-to-eck-1-1-0/232316/1 "2020-05-12T20:26:13Z")
Hi Team, My kibana ingress is not working after i upgraded to eck 1.1.0 from eck 1.0.1, below are the files for reference kibana\_cr.yaml ```auto apiVersion: kibana.k8s.elastic.co/v1 kind: Kibana metadata: name: kibana-config spec: version: 7.4.0 image: count: 1 elasticsearchRef: name: "elasticsearch-config" http: service: spec: type: LoadBalancer tls: selfSignedCertificate: disabled: true # this shows how to customize the Kibana pod # with labels and resource limits podTemplate: metadata: labels: kibana: node spec: containers: - name: kibana resources: limits: memory: 1Gi cpu: 1 --- apiVersion: extensions/v1beta1 kind: Ingress metadata: name: kibana-ingress spec: rules: - http: paths: - path: /* backend: serviceName: kibana-config-kb-http servicePort: 5601 ``` i cannot see any error in manifest but i am not able to view the webpage, the same config worked for previous release one more thing , i am able to see kibana dashboard using load balancer url but not able to see the same from ingress, which means my application is up and fine and so is my service , but ingress is not able to fetch me the webpage i am getting 502 error can you please help me with this ---
**Author:** ![charith-elastic](https://avatars.discourse-cdn.com/v4/letter/c/3ec8ea/32.png) [@charith-elastic](https://discuss.elastic.co/u/charith-elastic)\ **Post date:** [May 13, 2020, 6:48am UTC](https://discuss.elastic.co/t/kibana-ingress-not-working-after-upgrading-to-eck-1-1-0/232316/2 "2020-05-13T06:48:13Z")
Hi, this is possibly due to the Kibana readiness probe switching to an exec action in 1.1.0 (this was to support environments with strict network restrictions). Some ingress controllers require the probe to be an HTTP GET action in order to perform their own health checks. Try altering your Kibana manifest as follows: ```auto apiVersion: kibana.k8s.elastic.co/v1 kind: Kibana metadata: name: kibana-config spec: version: 7.4.0 image: count: 1 elasticsearchRef: name: "elasticsearch-config" http: service: spec: type: LoadBalancer tls: selfSignedCertificate: disabled: true # this shows how to customize the Kibana pod # with labels and resource limits podTemplate: metadata: labels: kibana: node spec: containers: - name: kibana resources: limits: memory: 1Gi cpu: 1 readinessProbe: httpGet: scheme: HTTPS path: "/login" port: 5601 ``` ---
**Author:** ![aman26ps](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aman26ps/32/82604_2.png) [@aman26ps](https://discuss.elastic.co/u/aman26ps)\ **Post date:** [May 13, 2020, 10:18am UTC](https://discuss.elastic.co/t/kibana-ingress-not-working-after-upgrading-to-eck-1-1-0/232316/3 "2020-05-13T10:18:12Z")
Thank you so much charith, its working fine now 🙂 ---
**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 18, 2021, 10:52am UTC](https://discuss.elastic.co/t/kibana-ingress-not-working-after-upgrading-to-eck-1-1-0/232316/4 "2021-03-18T10:52:19Z")
Hi everyone. Just have some questions about the above. - @aman26ps you are exposing kibana using behind an ingress, so why would you make the kibana service type `LoadBalancer`? - The second question is about overriding the Kibana healthcheck, I created an ingress using this config and it doesn't consider this, but point the health check to the root` /` of the pod. Any ideas about my case ? I'm using `ECK version 1.3.1`. Thank you in advance. ---
**Author:** ![Thibault\_Richard](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thibault_richard/32/50513_2.png) [@Thibault\_Richard](https://discuss.elastic.co/u/Thibault_Richard)\ **Post date:** [March 18, 2021, 1:59pm UTC](https://discuss.elastic.co/t/kibana-ingress-not-working-after-upgrading-to-eck-1-1-0/232316/5 "2021-03-18T13:59:42Z")
> The second question is about overriding the Kibana healthcheck, I created an ingress using this config and it doesn't consider this, but point the health check to the root ` /` of the pod. > Any ideas about my case ? Could you share your Kibana YAML manifest? ---
**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 18, 2021, 2:06pm UTC](https://discuss.elastic.co/t/kibana-ingress-not-working-after-upgrading-to-eck-1-1-0/232316/6 "2021-03-18T14:06:30Z")
Hi @Thibault_Richard, thanks for replying. Can we please move the discussion [here](https://discuss.elastic.co/t/exposing-kibana-behind-gke-ingress-unhealthy-state/267684). Thank you. ---
**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, 7:57am UTC](https://discuss.elastic.co/t/kibana-ingress-not-working-after-upgrading-to-eck-1-1-0/232316/7 "2022-11-04T07:57:57Z")