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
#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
The text was updated successfully, but these errors were encountered:
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.
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!
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
The text was updated successfully, but these errors were encountered: