From: Cyrus <cyruspy@gmail.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] API redundancy
Date: Fri, 14 Mar 2025 15:19:41 -0300 [thread overview]
Message-ID: <CAEaLa5FGttrRCTSU-0up2v=XUBfpr7vORFr7O0q9jqVhfpvbZQ@mail.gmail.com> (raw)
In-Reply-To: <743e060c-b095-4155-9fa7-1d086520a21a@anycast.cl>
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
next prev parent reply other threads:[~2025-03-14 18:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 16:59 Cyrus
2025-03-14 17:58 ` Roberto Alvarado
2025-03-14 18:19 ` Cyrus [this message]
2025-03-14 18:35 ` Roberto Alvarado
2025-03-14 19:36 ` Stefan Radman via pve-user
2025-03-14 18:37 ` Fabio Martins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAEaLa5FGttrRCTSU-0up2v=XUBfpr7vORFr7O0q9jqVhfpvbZQ@mail.gmail.com' \
--to=cyruspy@gmail.com \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal