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

multicluster: Provide High Availability mode for service-mirror component #8848

Closed
kleimkuhler opened this issue Jul 11, 2022 · 3 comments
Closed

Comments

@kleimkuhler
Copy link
Contributor

What problem are you trying to solve?

#7186 added HA mode for linkerd-multicluster's gateway component. We should investigate what is required for the service-mirror to also operate in HA mode.

How should the problem be solved?

The service-mirror was not designed to handle multiple service-mirror's watching the same cluster and keeping the local one mirrored correctly. Rather than just increasing the replicas configuration, we should look into leader election and see if they work well together.

Any alternatives you've considered?

Not right now but this should be part of the consideration.

How would users interact with this feature?

No response

Would you like to work on this feature?

No response

@stale
Copy link

stale bot commented Oct 12, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

@knutgoetz
Copy link
Contributor

Hey there, looks like most of the work was done by @mateiidavid in #11047 or am I mistaken? Maybe this can be closed? Anyway let me know if I can help. And thx @mateiidavid!

@mateiidavid
Copy link
Member

Thanks @knutgoetz! Seems that I forgot to link it against the PR. It can be closed! :)

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants