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
Is your feature request related to a problem? Please describe.
The OpAMP bridge right now is really only meant to be run as a single pod, there are users that would be interested in a high availability mode to ensure a reliable experience in Kubernetes in case of any pod evictions.
Describe the solution you'd like
Not sure yet... I think the method I like most so far is one where we use leader election to determine which pod is allowed to do remote configuration. That way we can scale up to multiple bridges while ensuring only one can write.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Component(s)
opamp
Is your feature request related to a problem? Please describe.
The OpAMP bridge right now is really only meant to be run as a single pod, there are users that would be interested in a high availability mode to ensure a reliable experience in Kubernetes in case of any pod evictions.
Describe the solution you'd like
Not sure yet... I think the method I like most so far is one where we use leader election to determine which pod is allowed to do remote configuration. That way we can scale up to multiple bridges while ensuring only one can write.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: