Keycloak Quarkus with 2 nodes

Hi everyone,

I’m testing Keycloak 18.0.0 with Quarkus.

I am impressed by the work done: congratulations to all the people working on the project :slight_smile:
It’s much easier to set up and configure :slight_smile:

I have seen this post:

In which dasniko explains there is no “domain” etc.

But I’m not sure I’m in the right direction to have 2 nodes (active/active or active/passive).
My need is simple:

  • worst case: in case of failure with my node 1, I would like to be up because of the node 2
  • nice case: to have an active/active cluster

What I did:

  • VM 1/3: I configured Nginx as reverse proxy + load balancer
  • VM 2/3: I installed/configured Keycloak 18.0.0
  • VM 3/3: I installed/configured Keycloak 18.0.0
  • my database is PostgreSQL:
    • master in VM 2/3
    • slave in VM 3/3

If I stop Keycloak in the VM 2/3, it seems it works: Nginx load balance to VM 3/3

But I have doubts…

Is it the good solution / approach?

How to deal with PostgreSQL database update?
For example should I configure spi-connections-jpa-default-migration-strategy:

  • to ‘update’ on VM 2/3
  • to ‘manual’ on VM 3/3
    To avoid a conflict?

Is it possible to have an active / active system with this edition based on Quarkus ?
If yes, how?

Sorry maybe I mis a documentation or something somewhere…
But all documentations related to HA I found seems related to Wildfly :confused:

Last question.
With the console in the previous versions, it was possible to deploy a theme directly to all nodes for example.
Is it possible with Quarkus?

Thank you very much :slight_smile:

I’m sorry to insist but does anyone know the answers please? :confused: