Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vdkjD-004IyB-0o for pgpool-general@arkaria.postgresql.org; Thu, 08 Jan 2026 07:46:44 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vdkjC-000zLT-0r for pgpool-general@arkaria.postgresql.org; Thu, 08 Jan 2026 07:46:43 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vdkjC-000zLL-0B for pgpool-general@lists.postgresql.org; Thu, 08 Jan 2026 07:46:42 +0000 Received: from mail-yx1-xb130.google.com ([2607:f8b0:4864:20::b130]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vdkjA-005EdE-0a for pgpool-general@lists.postgresql.org; Thu, 08 Jan 2026 07:46:42 +0000 Received: by mail-yx1-xb130.google.com with SMTP id 956f58d0204a3-640c9c85255so3199989d50.3 for ; Wed, 07 Jan 2026 23:46:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tailorbrands.com; s=google; t=1767858398; x=1768463198; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=widqhWzQUGIOdUFb2hW/byTB7TpJ7mZlExrJPcGILZo=; b=QAwIvfc9sZjw5DoZeWOJ+VicSR9KSyoqaozd1xBr6oqutozUhwta77HitGkEuL35oG nWxCF6bv+GU2dnX5JybvVtuEhIrCxCZAoscVhSW83WuXx0h1VSf4hPJujmitnwBMfcmJ /j3ZqQAL9UpFZ0G0Q2uPOAHuZ097OavQ96YLaXr91gx47kHHsQjFd0SinNxxiG9xquBH BIwybB5Ttgk+UBJYaRr9O5utC0hrSQYSV1jTLX4B25KAh+zp92wVCjc+mNbL/nG/pwFL z/R7JgEZ2/jiOEoPGDIlzLbtgpMiM0jIV3pN08C3n9Po2iT90rc3JI+pK+4EUDhBtQZ2 3ZQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1767858398; x=1768463198; h=cc:to:subject:message-id:date:from:mime-version:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=widqhWzQUGIOdUFb2hW/byTB7TpJ7mZlExrJPcGILZo=; b=natBkR9Sc5NVPCteKunsO1pch2pifw2N7a/WDiPdF8YsOTWDU1NBsZgM1nYOPXIstJ 7o3CG82prZWSMdyLQRBaxjCsoGfP4PyZfij3qU4hiFs429Zy8V6zIcBkzsufgirsztQe JmTAv6y3GZ2K5AveHyZc03u0FFIW62R8IaGyJMcPQtVDDcK0NkGQcYriC+J87VFiyTys 2VgxMoFtjsihCG0A/iEWXtvQ3ZKC5Wkv0X0ETwTeI7wm4fThIiZ7skIuBYh5IVadi14v Os6fMITqrI1XTzU8AHW6NEYwVFu9/Xg8FfCWe4OuAvIZD2i1Ix6+dMeOCEN5jjbedVFL r90g== X-Gm-Message-State: AOJu0YxIcnr6CPURzo0xsnzeF0A2k1CmI6o6EaZh71qbpgXV5hsLvg5Y nPvnMZMIQWHIRDkHa9+olXwVD/ZIVTirn4BdEzCOesv93U3+xD0sp9MG7/MGHOGNKfG4zCQ5z2d Ij9HDu1TBDni89X8FWlMI46jKyy+hVu/tlkR1OrfKS8W4mfzUNOmUHR8wxAvv X-Gm-Gg: AY/fxX6n5e0EOOnrsfpt4SOQcp2qlWrstapDflaJy1M/3Xax4rQ41AKjtr7AbwRpgTS IfHON9W9ipDrIyAUfuV05gQNDm8vjtRuxa2RLtaXSBkMViboxluazPRLRQ2QzsXy6S++AZNIt+x kuTItZgCZARWCCvvDu19M6m/7dU7mv3bP+tTIe6aP8A+GfvT4+xji9/ESlOqJne3V9+RIQuV6fG bI2PfzWf7w23cePRnVF/3dqV52yyBX1+IJoRiVaoQ1BQFNrkkMIrs05qTVr3I95utOY33zNU1N8 9x1MdFEun1aE43bB70kzjHbd8qf1EACDxHWj8mW4ziGG8SLeX6IYSw46xYsUz9sIAEpYEA4WooX iWas= X-Google-Smtp-Source: AGHT+IEJNJWzPVY4CiJdwKvWQmo+mXVPWtYexY5Ja7ys8auVKNKLdSh8Ivtj3GyOCB6d2vcsxirPiL9pVz26hUV4RFY= X-Received: by 2002:a05:690e:b4e:b0:644:774a:96b8 with SMTP id 956f58d0204a3-64716cd368cmr4539229d50.82.1767858398238; Wed, 07 Jan 2026 23:46:38 -0800 (PST) MIME-Version: 1.0 From: Nadav Shatz Date: Thu, 8 Jan 2026 09:46:26 +0200 X-Gm-Features: AQt7F2rcV-Bkr5OBusBngbLP3n7Bh2G5UZZn09CGaMbC-0BU2ornf7PJ-G5wLt8 Message-ID: Subject: pgpool2_on_k8s repo status To: pgpool-general@lists.postgresql.org Cc: platform-team@tailorbrands.com Content-Type: multipart/alternative; boundary="000000000000d7489b0647db9bab" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000d7489b0647db9bab Content-Type: text/plain; charset="UTF-8" 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 --000000000000d7489b0647db9bab Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi all,

I've noticed the= =C2=A0https://github.c= om/pgpool/pgpool2_on_k8s=C2=A0isn't getting a lot of attention with= very old issues, PR's not being merged or rejected=C2=A0and not much m= ovement there for a while.

Since Bitnami changed i= ts approach to releasing free charts and containers for Kubernetes, this re= po has become more relevant because there is no "best practice" o= pen source approach to running Pgpool in Kubernetes.

We are developing an updated and maintained approach and would much pref= er to share it with the community. This repository seems to be the best pla= ce to do so.

We are happy to contribute or assist = in any way we can to get the repo back on track.

P= lease let me know your suggested best approach moving forward.
--
Nadav Shatz
Tailor Brands=C2=A0| CTO
--000000000000d7489b0647db9bab--