Hello!,
Understanding there's not cluster IP (failover), how do you provide
redundancy for API consumers when one node is not accesible?
(User configured with API endpoint https://pve01:8006, pve01 going down,
pve02 accesible)
Regards.
___
pve-user mai
Hello!,
Yes, I can do it outside with a reverse proxy.
The message I'm rescuing: there's no transparent HA included out of the box
to cover that scenario
Regards.
On Fri, Mar 14, 2025, 14:59 Roberto Alvarado wrote:
> You can do this with nginx or haproxy, using each pve server as backend.
>
>
--- Begin Message ---
Hi Cyrus
Here is the simple keepalived configuration we're using.
It serves us very well for redundancy of the web GUI.
All you need is “apt install keepalived” on every cluster node and the
configuration in /etc/keepalived/keepalived.conf.
Just mind the different priorit
You can do this with nginx or haproxy, using each pve server as backend.
Saludos
Roberto
On 14-03-25 13:59, Cyrus wrote:
Hello!,
Understanding there's not cluster IP (failover), how do you provide
redundancy for API consumers when one node is not accesible?
(User configured with API endpoint
Demand easily included with a few diffs/additional packages. Likely your
proposition will be caught by a dev - meanwhile, you can do that even
with DNS / HAProxy / nginx / iptables / etc... as already suggested.
--Fabio
On 3/14/25 15:19, Cyrus wrote:
Hello!,
Yes, I can do it outside with a r
No, in proxmox this kind of sceneraio isnt resolved, other way (without
a reverse proxy) can be done with keepalived (vrrp), and use a "floating
IP"
Saludos
Roberto
On 14-03-25 15:19, Cyrus wrote:
Hello!,
Yes, I can do it outside with a reverse proxy.
The message I'm rescuing: there's no tr
