Backup Issued to Google Storage (GS)

PostgreSQL Percona Operator for PostgreSQL
1

Description:

Trying to get backup to a GCS bucket to work with either a S3 compatible pattern or Google storage pattern. Neither patter seems to work.

Steps to Reproduce:

Backup config:

  backups:
    pgbackrest:
      image: perconalab/percona-postgresql-operator:main-pgbackrest17
      configuration:
        - secret:
            name: dashboard-v2-6-0-pgbackrest-secrets
      global:
        repo1-path: /pgbackrest/postgres-operator/dashboard-v2-6-0/repo1
        repo1-retention-full: "7"
        repo2-path: /pgbackrest/developer-grafana12/postgres/dashboard-v2-6-0
        repo2-retention-full: "7"
      repoHost:
      manual:
        repoName: repo2
        options:
         - --type=full
      repos:
      - name: repo1
        volume:
          volumeClaimSpec:
            accessModes:
            - ReadWriteOnce
            resources:
              requests:
                storage: "20Gi"
      - name: repo2
        schedules:
          full: "0 0 * * 6"
          differential: "0 1 * * 1-6"
          incremental: "0 1 * * 1-6"
        gcs:
          bucket: "dev-dashboards"

dashboard-v2-6-0-pgbackrest-secrets

contains two data values:

gcs.conf: (base64 encoded)

[global]
repo2-gcs-key=/etc/pgbackrest/conf.d/gcs-key.json

gcs-key.json: (base64 of service file)

Trigger backup:

apiVersion: pgv2.percona.com/v2
kind: PerconaPGBackup
metadata:
  name: backuptest
spec:
  pgCluster: dashboard-v2-6-0
  repoName: repo2
  options:
    - --type=full

kubectl -n postgres-operator get PerconaPGBackup

backuptest   dashboard-v2-6-0   repo2                                             18m

Version:

2.6.0 Operator
Postgres 17

Logs:

kubectl -n postgres-operator logs pod/dashboard-v2-6-0-repo-host-0

Defaulted container "pgbackrest" out of: pgbackrest, pgbackrest-config, pgbackrest-log-dir (init), nss-wrapper-init (init)
P00   INFO: server command begin 2.55.0: --exec-id=71-94e46f60 --log-level-console=detail --log-level-file=off --log-level-stderr=error --log-path=/pgbackrest/repo1/log --no-log-timestamp --tls-server-address=0.0.0.0 --tls-server-auth=pgbackrest@9094c020-80d0-427a-ad1b-ad9df66de08e=* --tls-server-ca-file=/etc/pgbackrest/conf.d/~postgres-operator/tls-ca.crt --tls-server-cert-file=/etc/pgbackrest/server/server-tls.crt --tls-server-key-file=/etc/pgbackrest/server/server-tls.key

kubectl -n postgres-operator logs pod/dashboard-v2-6-0-repo-host-0 -c pgbackrest-config

environment: line 8: pkill: command not found
environment: line 2: pkill: command not found
environment: line 8: pkill: command not found
environment: line 2: pkill: command not found
environment: line 8: pkill: command not found
environment: line 2: pkill: command not found
environment: line 8: pkill: command not found
environment: line 2: pkill: command not found
environment: line 8: pkill: command not found

Expected Result:

Working backup

Actual Result:

No backup suceeded

Additional Information:

I’m currently testing this on K3D.

k3d version v5.6.0
k3s version v1.27.4-k3s1 (default)