public inbox for [email protected]  

help / color / mirror / Atom feed
From: Nadav Shatz <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: Re: pgpool2_on_k8s repo status
Date: Wed, 14 Jan 2026 10:56:20 +0200
Message-ID: <CACeKOO3aVyzmCCyTM9Z8=xOO1JDhv+jcE2pLO_jdh5azWcXVLQ@mail.gmail.com> (raw)
In-Reply-To: <CACeKOO0BeMb_q=cGBgR3Pd1E0ByqEeKfUcus_Fcm6VTsAk+8Fw@mail.gmail.com>
References: <CACeKOO0BeMb_q=cGBgR3Pd1E0ByqEeKfUcus_Fcm6VTsAk+8Fw@mail.gmail.com>

Hi all,

Any thoughts on the matter? would sharing is i pgpool-hackers be more
appropriate?

Best,

On Thu, Jan 8, 2026 at 9:46 AM Nadav Shatz <[email protected]> wrote:

> Hi all,
>
> I've noticed the https://github.com/pgpool/pgpool2_on_k8s isn't getting a
> lot of attention with very old issues, PR's not being merged or
> rejected and not much movement there for a while.
>
> Since Bitnami changed its approach to releasing free charts and containers
> for Kubernetes, this repo has become more relevant because there is no
> "best practice" open source approach to running Pgpool in Kubernetes.
>
> We are developing an updated and maintained approach and would much prefer
> to share it with the community. This repository seems to be the best place
> to do so.
>
> We are happy to contribute or assist in any way we can to get the repo
> back on track.
>
> Please let me know your suggested best approach moving forward.
>
> --
> Nadav Shatz
> Tailor Brands | CTO
>


-- 
Nadav Shatz
Tailor Brands | CTO


reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: pgpool2_on_k8s repo status
  In-Reply-To: <CACeKOO3aVyzmCCyTM9Z8=xOO1JDhv+jcE2pLO_jdh5azWcXVLQ@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox