public inbox for [email protected]help / color / mirror / Atom feed
pgpool2_on_k8s repo status 5+ messages / 2 participants [nested] [flat]
* pgpool2_on_k8s repo status @ 2026-01-08 07:46 Nadav Shatz <[email protected]> 0 siblings, 1 reply; 5+ messages in thread From: Nadav Shatz @ 2026-01-08 07:46 UTC (permalink / raw) To: [email protected]; +Cc: [email protected] 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 ^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: pgpool2_on_k8s repo status @ 2026-01-14 08:56 Nadav Shatz <[email protected]> parent: Nadav Shatz <[email protected]> 0 siblings, 1 reply; 5+ messages in thread From: Nadav Shatz @ 2026-01-14 08:56 UTC (permalink / raw) To: [email protected]; +Cc: [email protected] 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 ^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: pgpool2_on_k8s repo status @ 2026-01-14 13:18 Bo Peng <[email protected]> parent: Nadav Shatz <[email protected]> 0 siblings, 1 reply; 5+ messages in thread From: Bo Peng @ 2026-01-14 13:18 UTC (permalink / raw) To: Nadav Shatz <[email protected]>; [email protected] <[email protected]>; +Cc: [email protected] <[email protected]> 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 ^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: pgpool2_on_k8s repo status @ 2026-01-14 14:39 Nadav Shatz <[email protected]> parent: Bo Peng <[email protected]> 0 siblings, 1 reply; 5+ messages in thread From: Nadav Shatz @ 2026-01-14 14:39 UTC (permalink / raw) To: Bo Peng <[email protected]>; +Cc: [email protected] <[email protected]>; [email protected] <[email protected]> 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 ^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: pgpool2_on_k8s repo status @ 2026-01-15 11:02 Bo Peng <[email protected]> parent: Nadav Shatz <[email protected]> 0 siblings, 0 replies; 5+ messages in thread From: Bo Peng @ 2026-01-15 11:02 UTC (permalink / raw) To: Nadav Shatz <[email protected]>; +Cc: [email protected] <[email protected]>; [email protected] <[email protected]> Thank you for your understanding and for following up. We are hesitant to continue this repository under the current community ownership, even with external contributors, because we no longer have sufficient resources to support it, especially for testing against newer Kubernetes versions. Best regards, ________________________________________ 差出人: Nadav Shatz <[email protected]> 送信: 2026 年 1 月 14 日 (水曜日) 23:39 宛先: Bo Peng <[email protected]> Cc: [email protected] <[email protected]>; [email protected] <[email protected]> 件名: Re: pgpool2_on_k8s repo status 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 ShatzTailor Brands | CTOOn 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 statusHi 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 ^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2026-01-15 11:02 UTC | newest] Thread overview: 5+ messages (download: mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2026-01-08 07:46 pgpool2_on_k8s repo status Nadav Shatz <[email protected]> 2026-01-14 08:56 ` Nadav Shatz <[email protected]> 2026-01-14 13:18 ` Bo Peng <[email protected]> 2026-01-14 14:39 ` Nadav Shatz <[email protected]> 2026-01-15 11:02 ` Bo Peng <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox