public inbox for [email protected]
help / color / mirror / Atom feedFrom: Nadav Shatz <[email protected]>
To: Bo Peng <[email protected]>
Cc: [email protected] <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: pgpool2_on_k8s repo status
Date: Wed, 14 Jan 2026 16:39:15 +0200
Message-ID: <CACeKOO1HzD_dT9ACmjHKNP7wC9VRnr1pc-LwG1jpGY1XwRBFMg@mail.gmail.com> (raw)
In-Reply-To: <TYWP286MB2633544F4A280CFFBCB27D08F28FA@TYWP286MB2633.JPNP286.PROD.OUTLOOK.COM>
References: <CACeKOO0BeMb_q=cGBgR3Pd1E0ByqEeKfUcus_Fcm6VTsAk+8Fw@mail.gmail.com>
<CACeKOO3aVyzmCCyTM9Z8=xOO1JDhv+jcE2pLO_jdh5azWcXVLQ@mail.gmail.com>
<TYWP286MB2633544F4A280CFFBCB27D08F28FA@TYWP286MB2633.JPNP286.PROD.OUTLOOK.COM>
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 <[email protected]> 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 <[email protected]>
> SRA OSS K.K.
> URL: https://www.sraoss.co.jp/
>
> ________________________________________
> 差出人: Nadav Shatz <[email protected]>
> 送信: 2026 年 1 月 14 日 (水曜日) 17:56
> 宛先: [email protected] <
> [email protected]>
> Cc: [email protected] <[email protected]>
> 件名: 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 <
> [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 ShatzTailor
> Brands | CTO-- Nadav ShatzTailor 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], [email protected]
Subject: Re: pgpool2_on_k8s repo status
In-Reply-To: <CACeKOO1HzD_dT9ACmjHKNP7wC9VRnr1pc-LwG1jpGY1XwRBFMg@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