AKHQ behind AWS ELB

[caebozzini]

Using AKHQ v 0.18.0.
Chart ver.: 0.2.3

Sorry if this is a newbie issue (again), but I can't find a way to make AKHQ to load with a Kubernetes Ingress behind a AWS (internal) ELB.

As of now, I'm doing this:

micronaut:
    server:
      host-resolution:
        host-header: Host
        protocol-header: X-Forwarded-Proto

and this

ingress:
  enabled: true
  paths:
    - /
  hosts:
    - subdomain.domain.foo.bar

And this is what I see in the browser:

What am I missing?
Thanks and again sorry if this has an obvious response.

[ankurjains]

try disabling authentication and login with anonymous first if that is working ?

[caebozzini]

It isn't, behavior is the same regardless of the auth config.

[tchiotludo]

do you have some logs on the server side ?
I don't know any things about aws elb so I never tried myself.
Mostly seems that micronaut don't recognize the JWT cookie as I understand blindness

[wilkej]

I have a running setup with AWS ELB in front of AKHQ running within a kubernetes cluster. We have the same micronaut server configuration. Could you show the kubernetes ingress object created by the helm chart? I created the ingress on my own. This way I could try to compare them.

[tchiotludo]

I don't use the ingress by myself (since my loadbalancer is a treaffik with CRD ingress).
just download the charts and run a helm template . to see all the yaml from the helm charts