Running multiple instances of AKHQ

[naveen8384]

Hi,
We are trying to running multiple instances of AKHQ in kubernetes but after logging in and when we click on any menu item it is redirecting to login page.
It works well when we scale down AKHQ pods to 1.

Can someone help on running multiple akhq instance in Kubernetes?

[tchiotludo]

• What version of akhq are you using ?
• Are you using a common JWT secret on config or secrets ?

[naveen8384]

We are using akhq version 0.14.1 and secrets with basic-auth

[tchiotludo]

Really space here.
For the log, it's seems that you don't hit the endpoint (port 28081)

If you want to have a lot of logs :

curl -i -X POST -H "Content-Type: application/json" -d '{ "configuredLevel": "TRACE" }' http://localhost:28081/loggers/root

[naveen8384]

It worked with old version after adding these annotations to service
traefik.ingress.kubernetes.io/affinity: true,
traefik.ingress.kubernetes.io/session-cookie-name: sticky
and with 0.18.0 version I updated micronaut security config and it worked after that

[ankurjains]

@naveen8384 I am using basic auth . How i configure same basic auth like below with jwt secret. in my applicaiton.yml there is no jwt secret config but only basic auth i have given iwth single pod. So I want to run multiple pod now.

basic-auth:
- username: admin1 # Username
password: 8c6976e5b5410415bde908bd4dee15dfb167a9c873fc4bb8a81f6f2ab448a918
passwordHash: SHA256
groups: # Groups for the user
- admin
- username: appuser # Username
password: 8c6976e5b5410415bde908bd4dee15dfb167a9c873fc4bb8a81f6f2ab448a918
passwordHash: SHA256
groups: # Groups for the user
- topic-reader

[naveen8384]

To run multiple pods you have enable sticky sessions in service. If you are using traefik ingress then you need to add this two annotations in akhq values.yaml file

service:
  enabled: true
  type: ClusterIP
  port: 80
  annotations:
    traefik.ingress.kubernetes.io/affinity: "true"
    traefik.ingress.kubernetes.io/session-cookie-name: "sticky"

[ankurjains]

Yes 0.18.0 I used service without sticky in agic ingress controller / nginx too and no need to of sticky now

[tchiotludo]

Use the last version, there is no need to have a sticky session, since we don't use cookie on server side but JWT token that is consistent between node.