MIME-Version: 1.0
References: 
 <CACeKOO0BeMb_q=cGBgR3Pd1E0ByqEeKfUcus_Fcm6VTsAk+8Fw@mail.gmail.com>
 <CACeKOO3aVyzmCCyTM9Z8=xOO1JDhv+jcE2pLO_jdh5azWcXVLQ@mail.gmail.com>
 <TYWP286MB2633544F4A280CFFBCB27D08F28FA@TYWP286MB2633.JPNP286.PROD.OUTLOOK.COM>
In-Reply-To: 
 <TYWP286MB2633544F4A280CFFBCB27D08F28FA@TYWP286MB2633.JPNP286.PROD.OUTLOOK.COM>
From: Nadav Shatz <nadav@tailorbrands.com>
Date: Wed, 14 Jan 2026 16:39:15 +0200
Message-ID: 
 <CACeKOO1HzD_dT9ACmjHKNP7wC9VRnr1pc-LwG1jpGY1XwRBFMg@mail.gmail.com>
Subject: Re: pgpool2_on_k8s repo status
To: Bo Peng <pengbo@sraoss.co.jp>
Cc: "pgpool-general@lists.postgresql.org"
 <pgpool-general@lists.postgresql.org>,
	"platform-team@tailorbrands.com" <platform-team@tailorbrands.com>
Content-Type: multipart/alternative; boundary="00000000000038cf4006485a1388"
Archived-At: 
 <https://www.postgresql.org/message-id/CACeKOO1HzD_dT9ACmjHKNP7wC9VRnr1pc-LwG1jpGY1XwRBFMg%40mail.gmail.com>
Precedence: bulk

--00000000000038cf4006485a1388
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thank you for the reply. We=E2=80=99ll consider starting a fork. But why no=
t let us
try and contribute and manage this repo for now ?

Nadav Shatz
Tailor Brands | CTO


On Wed, Jan 14, 2026 at 3:18=E2=80=AFPM Bo Peng <pengbo@sraoss.co.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 wit=
h
> 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 an=
d
> manage it independently.
>
> We sincerely appreciate your initiative and your desire to share your wor=
k
> with the wider community, and we wish you the very best with your continu=
ed
> development. Please feel free to reach out if you have any questions or
> need clarification during the transition.
>
> Best regards,
> ---
> Bo Peng <pengbo@sraoss.co.jp>
> SRA OSS K.K.
> URL: https://www.sraoss.co.jp/
>
> ________________________________________
> =E5=B7=AE=E5=87=BA=E4=BA=BA: Nadav Shatz <nadav@tailorbrands.com>
> =E9=80=81=E4=BF=A1: 2026 =E5=B9=B4 1 =E6=9C=88 14 =E6=97=A5 (=E6=B0=B4=E6=
=9B=9C=E6=97=A5) 17:56
> =E5=AE=9B=E5=85=88: pgpool-general@lists.postgresql.org <
> pgpool-general@lists.postgresql.org>
> Cc: platform-team@tailorbrands.com <platform-team@tailorbrands.com>
> =E4=BB=B6=E5=90=8D: 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=E2=80=AFAM Nadav Shatz =
<
> nadav@tailorbrands.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 releasin=
g
> 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

--00000000000038cf4006485a1388
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Thank you for the reply. We=E2=80=99ll consider starting =
a fork. But why not let us try and contribute and manage this repo for now =
?<br clear=3D"all"><br clear=3D"all"><div><div dir=3D"rtl" class=3D"gmail_s=
ignature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr"><div><div dir=
=3D"ltr"><div dir=3D"rtl"><div dir=3D"ltr"><font style=3D"color:rgb(0,0,0)"=
>Nadav Shatz</font></div><div dir=3D"ltr"><font style=3D"color:rgb(0,0,0)">=
Tailor Brands=C2=A0| CTO</font></div></div></div></div></div></div></div></=
div><div><br></div><div><br><div class=3D"gmail_quote gmail_quote_container=
"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Jan 14, 2026 at 3:18=E2=80=
=AFPM Bo Peng &lt;<a href=3D"mailto:pengbo@sraoss.co.jp">pengbo@sraoss.co.j=
p</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-le=
ft:1ex;border-left-color:rgb(204,204,204)">Hi,<br>
<br>
Thank you very much for reaching out and for your thoughtful message. We tr=
uly appreciate your interest in Pgpool-II on Kubernetes and your willingnes=
s to contribute back to the community.<br>
<br>
You are absolutely right in your observations about the current state of th=
e repository. Given the rapid pace of Kubernetes evolution, maintaining thi=
s repository has become increasingly challenging for our community. In part=
icular, this repository relies on static YAML manifests to deploy Pgpool, w=
hereas the Kubernetes ecosystem has largely moved toward Helm charts and mo=
re automated, flexible deployment approaches. Keeping up with these best pr=
actices and frequent Kubernetes changes requires a level of ongoing effort =
that we are no longer able to sustain.<br>
<br>
As a result, our community is planning to place this repository into an End=
-of-Life (EOL) state and discontinue active maintenance going forward.<br>
<br>
Given your motivation to develop and maintain an updated approach, we belie=
ve the best path forward would be for you to fork this repository and manag=
e it independently. <br>
<br>
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 ne=
ed clarification during the transition.<br>
<br>
Best regards,<br>
---<br>
Bo Peng &lt;<a href=3D"mailto:pengbo@sraoss.co.jp" target=3D"_blank">pengbo=
@sraoss.co.jp</a>&gt;<br>
SRA OSS K.K.<br>
URL: <a href=3D"https://www.sraoss.co.jp/" rel=3D"noreferrer" target=3D"_bl=
ank">https://www.sraoss.co.jp/</a><br>
<br>
________________________________________<br>
=E5=B7=AE=E5=87=BA=E4=BA=BA: Nadav Shatz &lt;<a href=3D"mailto:nadav@tailor=
brands.com" target=3D"_blank">nadav@tailorbrands.com</a>&gt;<br>
=E9=80=81=E4=BF=A1: 2026 =E5=B9=B4 1 =E6=9C=88 14 =E6=97=A5 (=E6=B0=B4=E6=
=9B=9C=E6=97=A5) 17:56<br>
=E5=AE=9B=E5=85=88: <a href=3D"mailto:pgpool-general@lists.postgresql.org" =
target=3D"_blank">pgpool-general@lists.postgresql.org</a> &lt;<a href=3D"ma=
ilto:pgpool-general@lists.postgresql.org" target=3D"_blank">pgpool-general@=
lists.postgresql.org</a>&gt;<br>
Cc: <a href=3D"mailto:platform-team@tailorbrands.com" target=3D"_blank">pla=
tform-team@tailorbrands.com</a> &lt;<a href=3D"mailto:platform-team@tailorb=
rands.com" target=3D"_blank">platform-team@tailorbrands.com</a>&gt;<br>
=E4=BB=B6=E5=90=8D: Re: pgpool2_on_k8s repo status<br>
<br>
Hi all,Any thoughts on the matter? would sharing is i pgpool-hackers be mor=
e appropriate?Best,On Thu, Jan 8, 2026 at 9:46=E2=80=AFAM Nadav Shatz &lt;<=
a href=3D"mailto:nadav@tailorbrands.com" target=3D"_blank">nadav@tailorbran=
ds.com</a>&gt; wrote:Hi all,I&#39;ve noticed the=C2=A0<a href=3D"https://gi=
thub.com/pgpool/pgpool2_on_k8s" rel=3D"noreferrer" target=3D"_blank">https:=
//github.com/pgpool/pgpool2_on_k8s</a>=C2=A0isn&#39;t getting a lot of atte=
ntion with very old issues, PR&#39;s not being merged or rejected=C2=A0and =
not much movement there for a while.Since Bitnami changed its approach to r=
eleasing free charts and containers for Kubernetes, this repo has become mo=
re relevant because there is no &quot;best practice&quot; open source appro=
ach to running Pgpool in Kubernetes.We are developing an updated and mainta=
ined approach and would much prefer to share it with the community. This re=
pository 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 y=
our suggested best approach moving forward.-- Nadav ShatzTailor Brands=C2=
=A0| CTO-- Nadav ShatzTailor Brands=C2=A0| CTO</blockquote></div></div>

--00000000000038cf4006485a1388--