You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to DR my postgres cluster. I currently backup to 3 repos:
NFS via PVC
R2
Minio
I've repeatedly and successfully restored postgres clusters on a new k8s cluster via minio, however I'm running into a scenario where trying to do that via PVC/Volume fails, as it doesn't create the pod/PVC postgres-repo-host-0 until after the cluster is up and running. If I remove and recreate the cluster it works fine, but from a "blank" install of the operator it fails.
Environment
Kubernetes 1.32.1
Bare metal install (Talos Linux)
PGO ubi8-5..7.2-0
Postgres ubi-16.6-1 (16)
Storage local-hostpath (openebs)
Steps to Reproduce
Install PGO operator from scratch.
Create postgres cluster using dataSource.pgbackrest.repo.volume for the first time.
Pod fails to find data to restore from.
It appears to a condition where the PVC/Volume isn't created until after the cluster is successfully running.
EXPECTED
I'm able to successfully bootstrap a new cluster from a backup on an NFS system.
ACTUAL
The cluster hangs and is unable to bootstrap.
Logs
N/A, as I worked around it by bootstrapping from S3 to reduce downtime.
Overview
Hi team,
I'm trying to DR my postgres cluster. I currently backup to 3 repos:
I've repeatedly and successfully restored postgres clusters on a new k8s cluster via minio, however I'm running into a scenario where trying to do that via PVC/Volume fails, as it doesn't create the pod/PVC
postgres-repo-host-0
until after the cluster is up and running. If I remove and recreate the cluster it works fine, but from a "blank" install of the operator it fails.Environment
Kubernetes
1.32.1
Bare metal install (Talos Linux)
PGO
ubi8-5..7.2-0
Postgres
ubi-16.6-1
(16)Storage
local-hostpath
(openebs)Steps to Reproduce
Install PGO operator from scratch.
Create postgres cluster using
dataSource.pgbackrest.repo.volume
for the first time.Pod fails to find data to restore from.
It appears to a condition where the PVC/Volume isn't created until after the cluster is successfully running.
EXPECTED
I'm able to successfully bootstrap a new cluster from a backup on an NFS system.
ACTUAL
The cluster hangs and is unable to bootstrap.
Logs
N/A, as I worked around it by bootstrapping from S3 to reduce downtime.
Additional Information
This is an example of my
postgrescluster
that tried (and failed) to restore from PVChttps://github.com/joryirving/home-ops/blob/9614dc3d6bab8a53ddf7344890765e4f057c7827/kubernetes/main/apps/database/crunchy-postgres/cluster/cluster.yaml
Specifically here:
I'm manually creating the PV for the PVC to bind to here:
https://github.com/joryirving/home-ops/blob/9614dc3d6bab8a53ddf7344890765e4f057c7827/kubernetes/main/apps/database/crunchy-postgres/cluster/nfs-pvc.yaml
The text was updated successfully, but these errors were encountered: