Implementing Karavan in a load-balanced environment with mirrored nodes

[giorgiosiniscalchi]

Ask a question

Hi,

I am looking to implement Karavan in our environment and would appreciate some clarification on how to properly set it up. Let me explain our architecture:

• We have a load balancer that distributes requests to two identical, mirrored nodes.

• On each node, I would like to run both Karavan UI and the Docker environment that builds/deploys, so that both nodes have the same operational capabilities.

Here are my questions:

1. How should I manage configuration files, including application.properties, docker-compose.yml, Java files, and camel.yaml files? Is it better to have a centralized version of these files shared between the two nodes, or should each node have its own copy of the configuration files?

2. How should Karavan be handled in a load-balanced environment? Are there specific considerations or best practices to avoid synchronization issues between nodes? Can Karavan be configured to function smoothly on multiple nodes behind a load balancer?

3. Lastly, I would like to understand how route updates in Camel are managed in this load-balanced setup. For example, if I make an update to a Camel route via Karavan, how is this change propagated to both nodes? Do I need to manually synchronize the nodes, or is there an automatic mechanism to distribute the updates?

Thank you very much for your help!

Variant

Web Application

Container Management (if applicable)

Docker

Operating System (if applicable)

None

Version

4.8.0