Brent Graveland

https://kubernetes.io/docs/concepts/services-networking/service/#services-without-selectors Patroni is managing the endpoints, so the service is still usable, but patroni can use its better-understanding of the PostgreSQL cluster to make sure the service is always pointing...

Sure, that sounds pretty reasonable

It looks like pgdg is going to skip straight to 3.0.0, as that's what's in `bullseye-pgdg-testing` right now.

This repo builds on a schedule in order to incorporate upstream bug and security fixes, so this is expected.

You pick the level of comfort for changes that you're at: - pg16: pg minor versions and tsdb versions might update, along with system/pgdg things - pg16.2-ts2.14: the only thing...

Generally speaking, using `latest` is frowned upon when actually deploying things as you're supposed to pick something more explicit so you don't get surprised by changes. Also, we build multiple...

> @graveland Would you like me to make that change now? If you don't mind, thanks!

All good, thanks!