From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <pve-user-bounces@lists.proxmox.com> Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 333F51FF164 for <inbox@lore.proxmox.com>; Fri, 14 Mar 2025 19:35:45 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 9290F9BE8; Fri, 14 Mar 2025 19:35:31 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=anycast.cl; s=x; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:From:References:To: Subject:MIME-Version:Date:Message-ID:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=afIjmYAb6u67MreO80ZEHdFkSfXYxPPP0+QoCATrWU4=; b=QOaW/d/+tFLWuQsKdZRrYLQ1CW SwlmMRh4iK5ImOuLI3y9gIoq9M8zsu3GIcyc8ulArgx4fdEoH7kf2FZrJ3vlvruJJiMSaQQA5f/wM O3rvwqI5W/kbMjMj/YHgODkyfpHZyFTEniABA+h+MkK98ZisrX+p/Z2Hr3E0mXdd1lcirIWVIjVAH 6BW0dAzIe+sdfAPbJKpKX5rNrR61R6+m8h/H7kGwCnkxaq8A0InSgllJkwjiJsEcEdLTuFSfTC6Q5 mSRfWExTHpCKJ4XTBYxQB8Gk1l66RaqYDCnxaC8m1P4Bh8qFs6EwkBMhQ2evMLRd+LRxcB9lS7X/X yUWVH8FQ==; Message-ID: <da469486-9663-47e9-9d36-83e4013aa583@anycast.cl> Date: Fri, 14 Mar 2025 15:35:25 -0300 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: pve-user@lists.proxmox.com References: <CAEaLa5H4nZbR-O4uN=4vqbQyJqshgSytYD_DVOMnhqBRvxy1Sw@mail.gmail.com> <743e060c-b095-4155-9fa7-1d086520a21a@anycast.cl> <CAEaLa5FGttrRCTSU-0up2v=XUBfpr7vORFr7O0q9jqVhfpvbZQ@mail.gmail.com> Content-Language: es-ES From: Roberto Alvarado <ralvarado@anycast.cl> In-Reply-To: <CAEaLa5FGttrRCTSU-0up2v=XUBfpr7vORFr7O0q9jqVhfpvbZQ@mail.gmail.com> X-Authenticated-Id: ralvarado@anycast.cl X-SPAM-LEVEL: Spam detection results: 0 AWL -0.400 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain DMARC_MISSING 0.1 Missing DMARC policy KAM_ASCII_DIVIDERS 0.8 Email that uses ascii formatting dividers and possible spam tricks SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [anycast.cl, proxmox.com] Subject: Re: [PVE-User] API redundancy X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list <pve-user.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-user>, <mailto:pve-user-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-user/> List-Post: <mailto:pve-user@lists.proxmox.com> List-Help: <mailto:pve-user-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user>, <mailto:pve-user-request@lists.proxmox.com?subject=subscribe> Reply-To: Proxmox VE user list <pve-user@lists.proxmox.com> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: pve-user-bounces@lists.proxmox.com Sender: "pve-user" <pve-user-bounces@lists.proxmox.com> 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