cloudnative-pg / cloudnative-pg/plugin-barman-cloud
backup method changed in the output of kubectl get backup
- Lenguaje dominante
- Go
- Estrellas
- 191
- Forks
- 72
- Merge medio
- 2 d 21 h
- PR fusionados (30 d)
- 21
Descripción
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 ?
Guía de contribución
Línea de trabajo
The report centers on the Backup resource shown through `kubectl get backup` and the CNPG Barman plugin migration. First reproduce the migration from `barmanObjectStore` to `plugin` and inspect whether applying the new Backup manifest changes the existing object's METHOD; done means the original backup's method remains accurate or the behavior is documented as intentional.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- kubernetes, postgresql
- Área
- cloud, databases
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 35/100