-
Notifications
You must be signed in to change notification settings - Fork 20
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
docs: add high availability article #173
Conversation
Signed-off-by: mbshields <mshields@alum.mit.edu>
Signed-off-by: mbshields <mshields@alum.mit.edu>
docs/articles/high-availability.md
Outdated
|
||
Two failover configurations are possible: | ||
|
||
* Active/active |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would make active/active as second option.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Swapped order of A/S and A/A in the intro and in the configuration sections
docs/articles/high-availability.md
Outdated
|
||
An active/active zot registry can be implemented between two zot instances by configuring the `sync` extension in each instance to point to the other instance. In this scheme: | ||
|
||
* a load balancer such as HAProxy or a [DNS-based routing](https://coredns.io/plugins/loadbalance/) scheme is deployed for round-robin load balancing between zot instances |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Furthermore, one has to manage traffic split (path based routing) so some traffic goes to one instance and rest goes to another.
https://www.haproxy.com/blog/path-based-routing-with-haproxy
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this to keep a repo from being fragmented across two instances?
Signed-off-by: mbshields <mshields@alum.mit.edu>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
What type of PR is this?
documentation
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.