Re: pgpool2_on_k8s repo status

From: Nadav Shatz <nadav(at)tailorbrands(dot)com>
To: Bo Peng <pengbo(at)sraoss(dot)co(dot)jp>
Cc: "pgpool-general(at)lists(dot)postgresql(dot)org" <pgpool-general(at)lists(dot)postgresql(dot)org>, "platform-team(at)tailorbrands(dot)com" <platform-team(at)tailorbrands(dot)com>
Subject: Re: pgpool2_on_k8s repo status
Date: 2026-01-14 14:39:15
Message-ID: CACeKOO1HzD_dT9ACmjHKNP7wC9VRnr1pc-LwG1jpGY1XwRBFMg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgpool-general

Thank you for the reply. We’ll consider starting a fork. But why not let us
try and contribute and manage this repo for now ?

Nadav Shatz
Tailor Brands | CTO

On Wed, Jan 14, 2026 at 3:18 PM Bo Peng <pengbo(at)sraoss(dot)co(dot)jp> wrote:

> Hi,
>
> Thank you very much for reaching out and for your thoughtful message. We
> truly appreciate your interest in Pgpool-II on Kubernetes and your
> willingness to contribute back to the community.
>
> You are absolutely right in your observations about the current state of
> the repository. Given the rapid pace of Kubernetes evolution, maintaining
> this repository has become increasingly challenging for our community. In
> particular, this repository relies on static YAML manifests to deploy
> Pgpool, whereas the Kubernetes ecosystem has largely moved toward Helm
> charts and more automated, flexible deployment approaches. Keeping up with
> these best practices and frequent Kubernetes changes requires a level of
> ongoing effort that we are no longer able to sustain.
>
> As a result, our community is planning to place this repository into an
> End-of-Life (EOL) state and discontinue active maintenance going forward.
>
> Given your motivation to develop and maintain an updated approach, we
> believe the best path forward would be for you to fork this repository and
> manage it independently.
>
> We sincerely appreciate your initiative and your desire to share your work
> with the wider community, and we wish you the very best with your continued
> development. Please feel free to reach out if you have any questions or
> need clarification during the transition.
>
> Best regards,
> ---
> Bo Peng <pengbo(at)sraoss(dot)co(dot)jp>
> SRA OSS K.K.
> URL: https://www.sraoss.co.jp/
>
> ________________________________________
> 差出人: Nadav Shatz <nadav(at)tailorbrands(dot)com>
> 送信: 2026 年 1 月 14 日 (水曜日) 17:56
> 宛先: pgpool-general(at)lists(dot)postgresql(dot)org <
> pgpool-general(at)lists(dot)postgresql(dot)org>
> Cc: platform-team(at)tailorbrands(dot)com <platform-team(at)tailorbrands(dot)com>
> 件名: Re: pgpool2_on_k8s repo status
>
> 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 <
> nadav(at)tailorbrands(dot)com> 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 ShatzTailor
> Brands | CTO-- Nadav ShatzTailor Brands | CTO

In response to

Responses

Browse pgpool-general by date

  From Date Subject
Next Message Bo Peng 2026-01-15 11:02:42 Re: pgpool2_on_k8s repo status
Previous Message Bo Peng 2026-01-14 13:18:12 Re: pgpool2_on_k8s repo status