* [PVE-User] API redundancy @ 2025-03-14 16:59 Cyrus 2025-03-14 17:58 ` Roberto Alvarado 0 siblings, 1 reply; 6+ messages in thread From: Cyrus @ 2025-03-14 16:59 UTC (permalink / raw) To: Proxmox VE user list 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 mailing list pve-user@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PVE-User] API redundancy 2025-03-14 16:59 [PVE-User] API redundancy Cyrus @ 2025-03-14 17:58 ` Roberto Alvarado 2025-03-14 18:19 ` Cyrus 0 siblings, 1 reply; 6+ messages in thread From: Roberto Alvarado @ 2025-03-14 17:58 UTC (permalink / raw) To: pve-user 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 https://pve01:8006, pve01 going down, > pve02 accesible) > > Regards. > _______________________________________________ > pve-user mailing list > pve-user@lists.proxmox.com > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user > _______________________________________________ pve-user mailing list pve-user@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PVE-User] API redundancy 2025-03-14 17:58 ` Roberto Alvarado @ 2025-03-14 18:19 ` Cyrus 2025-03-14 18:35 ` Roberto Alvarado 2025-03-14 18:37 ` Fabio Martins 0 siblings, 2 replies; 6+ messages in thread From: Cyrus @ 2025-03-14 18:19 UTC (permalink / raw) To: Proxmox VE user list 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 <ralvarado@anycast.cl> wrote: > 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 https://pve01:8006, pve01 going down, > > pve02 accesible) > > > > Regards. > > _______________________________________________ > > pve-user mailing list > > pve-user@lists.proxmox.com > > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user > > > > _______________________________________________ > pve-user mailing list > pve-user@lists.proxmox.com > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user > > _______________________________________________ pve-user mailing list pve-user@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PVE-User] API redundancy 2025-03-14 18:19 ` Cyrus @ 2025-03-14 18:35 ` Roberto Alvarado 2025-03-14 19:36 ` Stefan Radman via pve-user 2025-03-14 18:37 ` Fabio Martins 1 sibling, 1 reply; 6+ messages in thread From: Roberto Alvarado @ 2025-03-14 18:35 UTC (permalink / raw) To: pve-user 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 transparent HA included out of the box > to cover that scenario > > Regards. > > On Fri, Mar 14, 2025, 14:59 Roberto Alvarado <ralvarado@anycast.cl> wrote: > >> 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 https://pve01:8006, pve01 going down, >>> pve02 accesible) >>> >>> Regards. >>> _______________________________________________ >>> pve-user mailing list >>> pve-user@lists.proxmox.com >>> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user >>> >> _______________________________________________ >> pve-user mailing list >> pve-user@lists.proxmox.com >> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user >> >> > _______________________________________________ > pve-user mailing list > pve-user@lists.proxmox.com > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user > _______________________________________________ pve-user mailing list pve-user@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PVE-User] API redundancy 2025-03-14 18:35 ` Roberto Alvarado @ 2025-03-14 19:36 ` Stefan Radman via pve-user 0 siblings, 0 replies; 6+ messages in thread From: Stefan Radman via pve-user @ 2025-03-14 19:36 UTC (permalink / raw) To: Proxmox VE user list; +Cc: Stefan Radman [-- Attachment #1: Type: message/rfc822, Size: 7986 bytes --] From: Stefan Radman <stefan.radman@me.com> To: Proxmox VE user list <pve-user@lists.proxmox.com> Subject: Re: [PVE-User] API redundancy Date: Fri, 14 Mar 2025 20:36:06 +0100 Message-ID: <C680BA8B-9899-42AC-96BD-1D206BEC8021@me.com> 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 priorities - gory details in the keepalived.conf(1) man page. The browser title page will show you which node you are actually connected to. Stefan root@pve01:~# host pve && echo && for node in pve01 pve02 pve03; do host $node && ssh $node cat /etc/keepalived/keepalived.conf && echo; done pve.example.com has address 10.10.10.10 pve01.example.com has address 10.10.10.1 vrrp_instance pve { interface vmbr1 virtual_router_id 10 priority 255 virtual_ipaddress { 10.10.10.10/24 } } pve02.example.com has address 10.10.10.2 vrrp_instance pve { interface vmbr1 virtual_router_id 10 priority 254 virtual_ipaddress { 10.10.10.10/24 } } pve03.example.com has address 10.10.10.3 vrrp_instance pve { interface vmbr1 virtual_router_id 10 priority 253 virtual_ipaddress { 10.10.10.10/24 } } > On Mar 14, 2025, at 19:35, Roberto Alvarado <ralvarado@anycast.cl> wrote: > > 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 transparent HA included out of the box >> to cover that scenario >> >> Regards. >> >> On Fri, Mar 14, 2025, 14:59 Roberto Alvarado <ralvarado@anycast.cl> wrote: >> >>> 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 https://pve01:8006, pve01 going down, >>>> pve02 accesible) >>>> >>>> Regards. >>>> _______________________________________________ >>>> pve-user mailing list >>>> pve-user@lists.proxmox.com >>>> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user >>>> >>> _______________________________________________ >>> pve-user mailing list >>> pve-user@lists.proxmox.com >>> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user >>> >>> >> _______________________________________________ >> pve-user mailing list >> pve-user@lists.proxmox.com >> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user >> > > _______________________________________________ > pve-user mailing list > pve-user@lists.proxmox.com > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user > [-- Attachment #2: Type: text/plain, Size: 157 bytes --] _______________________________________________ pve-user mailing list pve-user@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PVE-User] API redundancy 2025-03-14 18:19 ` Cyrus 2025-03-14 18:35 ` Roberto Alvarado @ 2025-03-14 18:37 ` Fabio Martins 1 sibling, 0 replies; 6+ messages in thread From: Fabio Martins @ 2025-03-14 18:37 UTC (permalink / raw) To: Proxmox VE user list, Cyrus 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 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 <ralvarado@anycast.cl> wrote: > >> 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 https://pve01:8006, pve01 going down, >>> pve02 accesible) >>> >>> Regards. >>> _______________________________________________ >>> pve-user mailing list >>> pve-user@lists.proxmox.com >>> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user >>> >> _______________________________________________ >> pve-user mailing list >> pve-user@lists.proxmox.com >> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user >> >> > _______________________________________________ > pve-user mailing list > pve-user@lists.proxmox.com > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user > -- Att. (+5521) 97914-8106 (Signal) PHOSPHORUS NETWORKS | HNO3 SYSTEMS https://www.linkedin.com/in/fabio1337br/ _______________________________________________ pve-user mailing list pve-user@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2025-03-14 19:42 UTC | newest] Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2025-03-14 16:59 [PVE-User] API redundancy Cyrus 2025-03-14 17:58 ` Roberto Alvarado 2025-03-14 18:19 ` Cyrus 2025-03-14 18:35 ` Roberto Alvarado 2025-03-14 19:36 ` Stefan Radman via pve-user 2025-03-14 18:37 ` Fabio Martins
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inboxService provided by Proxmox Server Solutions GmbH | Privacy | Legal