Open mkolesnik opened 3 years ago
This issue has been automatically marked as stale because it has not had activity for 60 days. It will be closed if no further activity occurs. Please make a comment if this issue/pr is still valid. Thank you for your contributions.
bump
This issue has been automatically marked as stale because it has not had activity for 60 days. It will be closed if no further activity occurs. Please make a comment if this issue/pr is still valid. Thank you for your contributions.
Epic Description
We need a service dedicated to syncing the broker information from the local cluster to the broker, and the broker info to the local cluster.
We have seen on scale testing that having the broker syncer inside the gateway causes issues to connectivity when there's a high enough scale.
Additionally, multiple projects (Submariner, Lighthouse) are using a specific broker syncer to sync over their resources. From an architectural POV it would be simpler if there was a "broker syncer" service which can sync resources to/from the remote broker, and the local services would only consume local resources. This decentralizes the information further, and decouples the services allowing the local services to easily keep working even if the broker is temporarily down. In addition, this opens up possibilities of easy broker HA since the data can be easily replicated.
This can also benefit Axon as it decouples the control plane information dissemination from Submariner, allowing alternative methods to be used.
Acceptance Criteria
Definition of Done (Checklist)
Work Items
submariner-brokersyncer
repository in Quay.iosubmariner-brokersyncer
insubmariner
repository (Wouldadmiral
be a better place?)subctl diagnose
subctl gather
subctl uninstall
submariner
lighthouse
submariner-brokersyncer
image toreleases
process