Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.100.0.2.22\))
Subject: Re: Running PostgreSQL in Kubernetes?
From: Scott Ribe <scott_ribe@elevated-dev.com>
In-Reply-To: <YP6QJja3b+2nZ3z7@admin.sibptus.ru>
Date: Mon, 26 Jul 2021 06:00:36 -0600
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <353A1D55-3DFF-43B1-B906-147C9C511435@elevated-dev.com>
References: <YP6QJja3b+2nZ3z7@admin.sibptus.ru>
To: Victor Sudakov <vas@sibptus.ru>
Archived-At: 
 <https://www.postgresql.org/message-id/353A1D55-3DFF-43B1-B906-147C9C511435%40elevated-dev.com>
Precedence: bulk

> Is anyone running PostgreSQL in Kubernetes? If you do, what solution =
do
> you prefer?=20
>=20
> What I've tried myself:
>=20
> 1. Running the official postgres:12.6 images in a StatefulSet. It =
works
> fine but there is neither failover nor replication.
>=20
> 2. Zalando's postgres-operator. Replication and failover work out of =
the
> box, but the documentation is not the best. Things like wal-g backup =
and
> PITR are probably possible, but you need to be an egghead to figure =
out
> how to make them work. Why, I cannot even figure out how to add a
> team after installing the postgres-operator from the official Helm =
repo.
>=20
> I'd be especially grateful if you shared your own personal experience
> with Kubernetes and PostgreSQL.

We're using CrunchyData's operator, which in turn uses Patroni & =
pgbackrest...