Is there an existing issue already for this bug?

• I have searched for an existing issue, and could not find anything. I believe this is a new bug.

I have read the troubleshooting guide

• I have read the troubleshooting guide and I think this is a new bug.

I am running a supported version of CloudNativePG

• I have read the troubleshooting guide and I think this is a new bug.

Contact Details

gabriele.fedi@enterprisedb.com

Version

1.27 (latest patch)

What version of Kubernetes are you using?

1.33

What is your Kubernetes environment?

Self-managed: kind (evaluation)

How did you install the operator?

YAML manifest

What happened?

When a CNPG Cluster is configured to perform WAL Archiving via CNPG-I Plugin, the CNPG operator doesn't behave as expected for new replicas creation.
The expectation is that, if a VolumeSnapshot backup is available and WAL archiving is enabled, the replica join operation is made through a restore from the VolumeSnapshot + WAL replication from the archive. The current behaviour is that even if the two mentioned options are valid, the join operation is done in the "standard way" through a pg_basebackup.

Cluster resource

apiVersion: postgresql.cnpg.io/v1
kind: Cluster
metadata:
  name: my-cluster
spec:
  backup:
    retentionPolicy: 1d
    target: primary
    volumeSnapshot:
      className: gp3-vsc
      online: true
      onlineConfiguration:
        waitForArchive: true
      snapshotOwnerReference: backup
  plugins:
  - enabled: true
    isWALArchiver: true
    name: barman-cloud.cloudnative-pg.io
    parameters:
      barmanObjectName: my-object-store

Relevant log output

Code of Conduct

• I agree to follow this project's Code of Conduct