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.

Sign up for GitHub

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

Jump to bottom

Support replicated app for multicluster #186

Closed
askmeegs opened this issue May 21, 2020 · 0 comments
Closed

Support replicated app for multicluster #186

askmeegs opened this issue May 21, 2020 · 0 comments
Labels
environments Anthos/GKE installation profiles + supported deploy targets priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@askmeegs
Copy link
Collaborator

Currently BoA supports multicluster (GKE + Istio) only when the services are split in half across clusters.

Validate the app (and make changes needed to) replicate all the services in multiple clusters - but sync database data so together, both clusters are one production instance of the app.

Purpose - demonstrate global high availability with Anthos.

For instance - run the entire app in cluster1 (us-centrl) and also in cluster2 (europe-west). Put Ingress For Anthos in front of both regions for the frontend. Then use Istio locality load balancing to "fall back" all traffic to cluster 2 if cluster1 goes down.

See #185 for DB replication tracking bug.

Brainstorming diagrams

More diagrams
@askmeegs askmeegs added what/feature New feature or request priority/P1 environments Anthos/GKE installation profiles + supported deploy targets labels May 21, 2020
@askmeegs askmeegs modified the milestones: v0.4.0 - Observability, security, v0.5.0 - High availability, Anthos install profiles Jun 9, 2020
@askmeegs askmeegs removed this from the v0.5.0 - Test infra integration + kustomize profiles milestone Jun 21, 2020
@JustinBeckwith JustinBeckwith added priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. and removed priority/P1 what/feature New feature or request labels Oct 13, 2020
@askmeegs askmeegs mentioned this issue Nov 25, 2020
Closed
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
environments Anthos/GKE installation profiles + supported deploy targets priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@JustinBeckwith @askmeegs