You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 4, 2023. It is now read-only.
Related issue for elasticsearch with some ideas on how we can generalise
attributes of hosts that the DB runs on, and make the database aware of the
topology of the system.
I'd rather avoid introducing terms like "zone" and "data centre" in favour
of arbitrary labels on nodes and pods. This is how kubernetes represents
failure domains without assuming anything about the topology.
#44
This is pretty complex, as a Kubernetes cluster is usually homed in a single region, and federation doesn't seem like it'll be a major theme in Kubernetes multi-cluster in future.
We would need some way to federate Navigator itself in this instance. We'd also need to think about how we'd manage HA for pilot-controller across clusters, and how that'd work.
This blog suggests creating a statefulset per DC.
So perhaps we can have a Navigator NodePool per datacentre.
We should consider that.
/feature
The text was updated successfully, but these errors were encountered: