Wanting to have an (off-site) standby replica of your Postgres instance? Patroni and Zalando Postgres Operator can help you here. By either having a constant streaming from your primary cluster, or by applying WAL archives constantly as you backup them to S3 storage.
Read More »Sleep until promoted – Using Zalando Postgres Operator for Standby Postgres setup
The Zalando Postgres Operator has a built in possibility to maintain a PgBoucer setup for your Postgres cluster. But what is PgBouncer and why should… Read More »Handle this – PostgreSQL PgBouncer setup with Zalando Postgres Operator
You want to have a proper ingress handling for your Postgres databases running on Kubernetes? With external DNS registration and signed certificates? Then you’re absolutely right here.
Read More »Ingress detected – Configure Ingress for Postgres on Kubernetes
Since I rely heavily on the Zalando Spilo image as Postgres setup in my Kubernetes Homelab, I wanted to have those WAL-G backups that I make also within my Prometheus / Grafana setup. I had a look on existing solutions and found only but one which is no longer actively maintained as it seems. So I took this Prometheus WAL-G metric exporter written in Python, and made it working for me. I want to show you, how I use it as a sidecar on my Spilo Postgres pods and what is the outcome of it.
Read More »Get me those metrics – Use Prometheus WAL-G backup exporter
Patroni is a reliable cluster software for Postgres which, when running on Kubernetes, can use the Kubernetes API itself as DCS (Distributed Config Store). This is very nice, but on Kubernetes clusters with an unreliable API / Controlplane, this can lead to demotion of your cluster leader and thereby unhappy users. Gladly, Patroni supports other setups as DCS like etcd.
Read More »Using etcd as Patroni DCS with the Zalando Postgres Operator
WAL-G is a widely known backup software for Postgres databases. One of it’s features is to backup to S3 storage out of the box. Also it’s capable to encrypt those backups and WAL archives with several encryption methods (e.g. libsodium). Since WAL-G is implemented within the Zalanndo Spilo image and therefore deployed by default with the Zalando Postgres Operator on Kubernetes, I had a deeper look on how to get encrypted backups implemented there, cause this is not documented well.
Read More »A pinch of salt – Encrypt WAL-G PostgreSQL backups
SQL Profiles are a powerful tool to improve performance of SQL queries in your Oracle Database. Most of the time, you implement them by the output of a SQL Tuning Task, but did you know, that you can write your own SQL Profile manually?
Read More »Manual creation of SQL Profiles in Oracle Database
Oracle want’s to participate in the open source movement lately, making itself known as “an Open Source company”. Part of this is the Oracle Database Operator for Kubernetes. It’s an early version (0.1.0) that I’ve tested out, so it offers only a limited set of features as of now. Let’s move it to it’s paces, shall we?
Read More »Bastard Operator from Hell? – Giving the Kubernetes Oracle Database Operator a try
In an earlier blogpost, I wrote about doing Postgres backups using WAL-G to a S3 storage. This time we have a look to either clone or “inplace” restore a postgres instance from these backups. All of this using the Zalando Postgres Operator. If you haven’t done so, please read the backup post before proceeding reading this one.
Read More »Restore and Clone from S3 – Configure Zalando Postgres Operator Restore with WAL-G
Doing basebackups of Postgres databases enables you to do a Point-in-time recovery (PITR) of your database. Doing backups for your databases that have been deployed using the Zalando Postgres Operator, is a different beast. Here I show you how it’s done with a MinIO (self)hosted S3 compatible Object Storage.
Read More »Backup to S3 – Configure Zalando Postgres Operator Backup with WAL-G