Ingress for ECK Kibana

[telapo (Davide)]

Hi, I have followed the documentation to deploy ECK on Kubernetes (local testing on docker for mac), and everything is working fine, elastic is up and running and Kibana is connected to it. I can port forward it, and I am able to login and query elastic. However, I am really struggling to find an example of an ingress for Kibana. This is one of my attempt:

apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
  name: k-ingress
  annotations:
    kubernetes.io/ingress.class: traefik
spec:
  rules:
    - host: kibana.host.com
      http:
        paths:
          - backend:
              serviceName: kibana-kb-http
              servicePort: 5601
            path: /

As you may have seen, I am using Traefik.

Could you help me setup an Ingress, please?

[stephenb (Stephen Brown)]

Here is an example I did with the default GKE perhaps it will help.

Is Kibana supported on GKE through default google ingress ? doesn't seem so

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…

[telapo (Davide)]

Hi @stephenb, thank you for your reply.

I actually went back to the documentation and found out that it was enough to:

apiVersion: kibana.k8s.elastic.co/v1
kind: Kibana
metadata:
  name: kibana
  labels:
    various...
spec:
  version: 7
  http: # I did not have it before
    service:
      spec:
        type: LoadBalancer
    tls: # I put it in the wrong place before
      selfSignedCertificate:
        disabled: true
  count: 1
  elasticsearchRef:
    name: "elasticsearch"
  podTemplate:
    containers:
      - name: kibana
        resources:
          limits:
            memory: 2Gi
            cpu: 2

I could then load Kibana using http://my-cluster:5601. So, the httppart was key to have Kibana exposed.