Ingress for Kibana dashboard when using kubernetes & traefik

Dear Colleagues,

I've followed a get started guide on

I've deployed es + kibana in the way described there.
If I curl from master instance , it works

curl -I -k -u elastic:$PASSWORD
HTTP/1.1 200 OK
content-security-policy: script-src 'unsafe-eval' 'nonce-xxxxxxxxx'; worker-src blob:; child-src blob:
kbn-name: kibana
kbn-xpack-sig: 24402aaf1221ff23f12f12f12f12f12f
cache-control: no-cache
content-type: text/html; charset=utf-8
content-length: 81330
vary: accept-encoding
connection: close
Date: Thu, 03 Sep 2019 11:23:25 GMT

Though, in front of kibana there is a traefik LB
So, if I would go to a mapped route /kibana (mapped to kibana service + 5601 port) , this results in a redirection to "login?next=%2F"

HTTP/1.1 302 Found
location: /login?next=%2F
kbn-name: kibana
kbn-xpack-sig: 24402ca2235df0b3dc31c96be2fbfa3a
content-type: text/html; charset=utf-8
cache-control: no-cache

So, kibana redirects to a wrong base path.
In documentation i found that there is a possibility to set a base path like :

    value: /api/xxx

How to better implement it taking into account implementation in

Found the solution.
Apparently, in earlier versions <0.9 of eck operator this was not possible and was a limitation.

Now, starting for version 0.9 SERVER_BASEPATH via env is supported and a lot more.

To check the eck operator version, looks in kind: StatefulSet - name: elastic-operator > ,

Solution (in kibana operator file):

        app: kibana
        function: logging
      - name: kibana
          - name: SERVER_BASEPATH
            value: /kibana

Found this in :

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