Run Multiple Paladins on Multiple Nodes (Networks)

[dwertent]

Overview

The goal is to deploy multiple Paladin Docker containers on separate nodes (networks), where each Paladin instance runs on its own network and connects to a corresponding Besu node. Additionally, the Paladin containers across different nodes must be able to communicate with each other.

This issue is dependent on Run Paladin in a Multi-Node Setup (Multiple Containers).

It can be achieved by:

• Creating multiple Docker networks and assigning each Paladin container to a different network.
• Running in Kubernetes with each Paladin in a separate namespace, routing the networks between Paladin instances via IPs.

Assumptions

• The Paladin engine serves as the testbed
• The primary focus of the test is to verify that different Paladin services can communicate with each other across nodes
• Logs will confirm successful communication between Paladin instances and that they are receiving block events from their respective Besu nodes

DoD

• Multiple Paladin containers are deployed on separate nodes (each using its own network or namespace)
• Each Paladin instance is connected to a different Besu node within its respective network
• Paladin containers are able to successfully communicate with each other across the separate nodes, exchanging relevant data
• Logs confirm that Paladin instances can both receive block events from Besu and communicate with other Paladin services

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity.