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

docs: add high availability article #173

Merged
merged 3 commits into from
Jun 24, 2024

Conversation

mbshields
Copy link
Contributor

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.

Signed-off-by: mbshields <mshields@alum.mit.edu>
@mbshields mbshields requested a review from rchincha June 21, 2024 03:42
Signed-off-by: mbshields <mshields@alum.mit.edu>
@rchincha rchincha requested review from andaaron June 24, 2024 15:57

Two failover configurations are possible:

* Active/active
Copy link
Contributor

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.

Copy link
Contributor Author

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


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
Copy link
Contributor

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

Copy link
Contributor Author

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>
Copy link
Contributor

@rchincha rchincha left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@rchincha rchincha merged commit a19141e into project-zot:main Jun 24, 2024
6 checks passed
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

Successfully merging this pull request may close these issues.

2 participants