[GH-ISSUE #928] Support Keepalived in a Cluster #496

New issue

Open

opened 2026-02-26 12:08:31 +03:00 by kerem · 0 comments

kerem commented

2026-02-26 12:08:31 +03:00

Owner

Originally created by @riebecj on GitHub (Mar 22, 2025).
Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/928

Is your feature request related to a problem? Please describe.
No related problem.

Describe the solution you'd like
Have the UI support a keepalived VIP configuration between the nodes. This would require managing the /etc/keepalived/keepalived.conf file, but at a minimum it would require a vrrp_instance on each node, you could use the same node name/secret from the primary node when configuring authentication and pidof nginx-ui and/or systemctl is-active --quiet nginx-ui in the vrrp_script for each node's vrrp_instance. This would allow for a cluster of NginxUI nodes to be HA and fault tolerant.

Describe alternatives you've considered
Manually deploying keepalived to the NginxUI nodes via a separate pipeline.

Additional context
N/A

Originally created by @riebecj on GitHub (Mar 22, 2025). Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/928 **Is your feature request related to a problem? Please describe.** No related problem. **Describe the solution you'd like** Have the UI support a `keepalived` VIP configuration between the nodes. This would require managing the `/etc/keepalived/keepalived.conf` file, but at a minimum it would require a `vrrp_instance` on each node, you could use the same node name/secret from the primary node when configuring authentication and `pidof nginx-ui` and/or `systemctl is-active --quiet nginx-ui` in the `vrrp_script` for each node's `vrrp_instance`. This would allow for a cluster of NginxUI nodes to be HA and fault tolerant. **Describe alternatives you've considered** Manually deploying `keepalived` to the NginxUI nodes via a separate pipeline. **Additional context** N/A