New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cross Site - Gossip Router tunnel support #1201
Conversation
86c10be
to
032f667
Compare
7755fc3
to
ef15708
Compare
265ad36
to
64ae91c
Compare
64ae91c
to
8c38421
Compare
Also we need to watch Deployment resources to catch unpredictable resource remove/delete/update |
I wasn't aware of that. Is there any example in the code? |
You should add
|
8c38421
to
734976d
Compare
734976d
to
48cf042
Compare
updated the code to use Also, just crossed my mind, I should add some readiness and liveness probes to GossipRouter pod. |
48cf042
to
5b9b08d
Compare
code updated. Status:
Conditions:
Status: True
Type: PreliminaryChecksPassed
Status: True
Type: GossipRouterReady
Message: View: test-cross-site-view-internal-xsite2-0-63738
Status: True
Type: WellFormed
Message: Cross-Site view: xsite1,xsite2
Status: True
Type: CrossSiteViewFormed |
5b9b08d
to
8a85046
Compare
updated. |
Using Gossip Router and TUNNEL transport for cross-site replication between Infinispan clusters
If you're happy with the changes @dmvolod I will merge |
Yes, @ryanemerson looks good, thanks |
Thanks @pruivo |
Good point @dmvolod. FYI @gustavonalle |
Adds support to use JGroups' TUNNEL protocol with GossipRouter pods.
It uses the JGroups JAR inside the server image to avoid depending on another image.
PR is open to get feedback sooner than later. No rush to integrate yet.
TODO: