-
Notifications
You must be signed in to change notification settings - Fork 36
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
flagd-proxy HA setup #609
Comments
@xvzf I like this idea. I think maybe we should default to 2 instances. I think an additional config option makes sense, but I'm interested in the opinions of others... @odubajDT @Kavindu-Dodan @thisthat what do you think? It seems #524 is pretty stale, I'm going to close it. |
We could do this through environment variables dedicated to proxy [1]. And regarding the need for replicas, I assume this is to provide HA for your use case and I think this is a good overal improvement. |
I think having HA for a central component like the proxy definitely makes sense 👍 |
I'll come up with a draft PR in the next days :) |
Somebody mentioned this specific issue at KubeCon, so I guess you're right @xvzf |
FYI picked this up now 👍 |
Based on the behaviour observed and the fixed replica count of
1
(ref), I'm wondering if it makes to have two or more instances of the flagd-proxy running in combination with a PodDisruptionBudget.I can work on this (either as a config option or extending the schema similar to what's currently discussed in #524), but wanted to ask for feedback here first!
The text was updated successfully, but these errors were encountered: