cloudnative-pg / cloudnative-pg/plugin-barman-cloud

backup method changed in the output of kubectl get backup

Ouverte
#602 2 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
question
Langage dominant
Go
Étoiles
191
Forks
72
Merge moyen
2 j 21 h
PR mergées (30 j)
21

Description

Hi, Team !

I have my CNPG 1.26.1 cluster with Barman Native configured.

```
tee $cluster_name.yaml << EOF
apiVersion: postgresql.cnpg.io/v1
kind: Cluster
metadata:
name: $cluster_name
namespace: $oname-system
spec:
instances: 3
imageName: $cnpg_image_name
storage:
size: 1Gi
backup:
retentionPolicy: "1d"
barmanObjectStore:
destinationPath: s3://cluster-backups/
endpointURL: http://minio-service:9000
s3Credentials:
accessKeyId:
name: minio-creds
key: ACCESS_KEY_ID
secretAccessKey:
name: minio-creds
key: ACCESS_SECRET_KEY
wal:
compression: gzip
EOF
```

```
tee barman-backup.yaml << EOF
apiVersion: postgresql.cnpg.io/v1
kind: Backup
metadata:
name: barman-backup
namespace: $oname-system
spec:
cluster:
name: $cluster_name
target: prefer-standby
EOF
```

I have two backups:
- `barman-backup` is done by `kubectl apply -f barman-backup.yaml`
- `cluster-barman-cnpg-20251016101137` is done by `kubectl cnpg -n $oname-system backup $cluster_name -m barmanObjectStore`

```
[alexey@wsl2 ~]$ kubectl get -n $oname-system backup
NAME AGE CLUSTER METHOD PHASE ERROR
barman-backup 57s cluster-barman-cnpg barmanObjectStore completed
cluster-barman-cnpg-20251016101137 6s cluster-barman-cnpg barmanObjectStore completed
```

Now I'm migrating to Barman Plugin 0.7.0:

```
tee $cluster_name.yaml << EOF
apiVersion: postgresql.cnpg.io/v1
kind: Cluster
metadata:
name: $cluster_name
namespace: $oname-system
spec:
instances: 3
imagePullPolicy: Always
imageName: $cnpg_image_name
storage:
size: 1Gi
plugins:
- name: barman-cloud.cloudnative-pg.io
isWALArchiver: true
parameters:
barmanObjectName: minio-store
EOF
```

```
tee barman-backup.yaml << EOF
apiVersion: postgresql.cnpg.io/v1
kind: Backup
metadata:
name: barman-backup
namespace: $oname-system
spec:
cluster:
name: $cluster_name
method: plugin
pluginConfiguration:
name: barman-cloud.cloudnative-pg.io
target: prefer-standby
EOF
```

After launching `kubectl apply -f barman-backup.yaml` I have the following:

```
[alexey@wsl2 ~]$ kubectl get -n $oname-system backup
NAME AGE CLUSTER METHOD PHASE ERROR
barman-backup 14m cluster-barman-cnpg plugin completed
cluster-barman-cnpg-20251016101137 13m cluster-barman-cnpg barmanObjectStore completed
```

So, somehow the `METHOD` for my older `barman-backup` backup has been changed from `barmanObjectStore` to `plugin`:

```
[alexey@wsl2 ~]$ kubectl get -n $oname-system backup
NAME AGE CLUSTER METHOD PHASE ERROR
barman-backup 57s cluster-barman-cnpg barmanObjectStore completed
cluster-barman-cnpg-20251016101137 6s cluster-barman-cnpg barmanObjectStore completed
```

Is it by design ? If not, can it be fixed ?

Guide de contribution

Ouvrir le guide de contribution

Piste de recherche

Le rapport porte sur la ressource Backup affichée via `kubectl get backup` et sur la migration du plugin Barman de CNPG. Reproduisez d’abord la migration de `barmanObjectStore` vers `plugin` et vérifiez si l’application du nouveau manifeste Backup modifie la METHOD de l’objet existant ; c’est terminé lorsque la METHOD du backup d’origine reste correcte ou que le comportement est documenté comme intentionnel.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
kubernetes, postgresql
Domaine
cloud, databases
Type d'issue
Bug
Difficulté
4/5
Temps estimé
3-5 jours
Activité
À l'abandon
Clarté
À clarifier
Accessibilité débutants
35/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.