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.
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
The text was updated successfully, but these errors were encountered:
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 avrrp_instance
on each node, you could use the same node name/secret from the primary node when configuring authentication andpidof nginx-ui
and/orsystemctl is-active --quiet nginx-ui
in thevrrp_script
for each node'svrrp_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
The text was updated successfully, but these errors were encountered: