-
Notifications
You must be signed in to change notification settings - Fork 468
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
recommend regional over zonal clusters in K8s deployment docs #10479
Comments
We should also look through the README for multi-region in the CRDB repo which is also out of date. /cc @keith-mcclellan |
e.g. External LB requirement is wrong if I understand what it's trying to do, you can hit internal LB from any region in google now |
@udnay I think I'm missing something, but based on Ben's comment in #4640, it sounds like each node needs to specify a separate AZ on start? I'm unsure how we can do that based on our STS configs, which use a single start command and specify 3 replicas. Let me know if this should be a separate issue. |
We have marked this issue as stale because it has been inactive for |
Yandu Oppacher (udnay) commented:
The current multi-site guides use zonal clusters for the reference implementation. These should be regional clusters to ensure proper redundancy and matching SLA requirements within a region.
e.g.
Would only get a customer "single instance uptime" SLA of
99.5
instead of99.99
for regional workloads. There is similarly a lower SLA for zonal GKE clusters. We should update the docs to reflect this.Jira Issue: DOC-1605
The text was updated successfully, but these errors were encountered: