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.

Sign up for GitHub

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

Jump to bottom

High availability for Docker Engine #3778

Open
zackwasli opened this issue Apr 25, 2024 · 1 comment
Open

High availability for Docker Engine #3778

zackwasli opened this issue Apr 25, 2024 · 1 comment
Labels
feature-request New feature or request that needs to be turned into Epic/Story details needs-triage Needs looking at to decide what to do

Comments

@zackwasli
Copy link
Contributor

Description

Today we have High Availability for Kubernetes environments. However, Docker environments do not have HA capabilities. Since we offer self-hosted deployment of FlowFuse within both Docker and Kubernetes, it would be ideal to have feature parity among these setups as well.

Requested by:

https://app-eu1.hubspot.com/contacts/26586079/record/0-2/10135626714

Which customers would this be available to

Enterprise Tier Only (EE)

Have you provided an initial effort estimate for this issue?

I have provided an initial effort estimate
@zackwasli zackwasli added feature-request New feature or request that needs to be turned into Epic/Story details needs-triage Needs looking at to decide what to do labels Apr 25, 2024
@hardillb
Copy link
Contributor

hardillb commented Apr 25, 2024 •
edited

While the nginx-proxy will load balance across 2 containers with the same VIRTUAL_HOST env var, this would need a large bit of work to replicate what we get for free with Kubernetes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature-request New feature or request that needs to be turned into Epic/Story details needs-triage Needs looking at to decide what to do
Projects
☁️ Product Planning
Status: No status
Milestone
No milestone
Development

No branches or pull requests
2 participants
@hardillb @zackwasli