Skip to content
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

Document how to make a multi site configuration #58

Open
bryopsida opened this issue Aug 31, 2024 · 1 comment
Open

Document how to make a multi site configuration #58

bryopsida opened this issue Aug 31, 2024 · 1 comment

Comments

@bryopsida
Copy link
Owner

bryopsida commented Aug 31, 2024

We currently only document a single site setup, it should be possible to use multiple deployments each connecting to each other.

Specifically this scenario

                A
              |   |
            |       |
          |           |
         B             C

B cluster can route/connect to A but its clients cannot directly route to A
B cluster cannot route directly to C
C cluster can route/connect to A but its clients cannot directly route to A
C cluster cannot route directly to B

B site connects to A
C site connects to A

cluster service discovery is not available to peers as that would likely require deconflicting the cluster domains and routing dns to the appropriate kube dns or synchronizing entries using something such as external-dns and extending the cluster dns with record synchronized across the nodes via that.

B peers can connect C peers and vice versa, WAN egress could go through A.

@bryopsida
Copy link
Owner Author

Likely would need to add something to share peer routes across WG server pods in same cluster.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant