generated from cloudnative-pg/cnpg-template
-
Notifications
You must be signed in to change notification settings - Fork 55
Closed
cloudnative-pg/cloudnative-pg
#8780Labels
bugSomething isn't workingSomething isn't working
Description
Hi, Team !
I have a plugin barman 0.6.0 setup with CNPG 1.27.0 and the following Minio configuration:
tee minio.yaml << EOF
apiVersion: v1
kind: Secret
metadata:
name: minio-creds
data:
ACCESS_KEY_ID: $ACCESS_KEY_ID
ACCESS_SECRET_KEY: $ACCESS_SECRET_KEY
---
apiVersion: v1
kind: Service
metadata:
name: minio-service
spec:
ports:
- port: 9000
targetPort: 9000
protocol: TCP
selector:
app: minio
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: minio
spec:
selector:
matchLabels:
app: minio
template:
metadata:
labels:
app: minio
spec:
containers:
- name: minio
image: minio/minio:latest
args:
- server
- /data
env:
- name: MINIO_ACCESS_KEY
valueFrom:
secretKeyRef:
name: minio-creds
key: ACCESS_KEY_ID
- name: MINIO_SECRET_KEY
valueFrom:
secretKeyRef:
name: minio-creds
key: ACCESS_SECRET_KEY
ports:
- containerPort: 9000
readinessProbe:
httpGet:
path: /minio/health/ready
port: 9000
initialDelaySeconds: 30
livenessProbe:
httpGet:
path: /minio/health/live
port: 9000
initialDelaySeconds: 30
EOF
ObjectStore configuration is:
tee minio-store.yaml << EOF
apiVersion: barmancloud.cnpg.io/v1
kind: ObjectStore
metadata:
name: minio-store
spec:
configuration:
destinationPath: s3://cluster-backups/
endpointURL: http://minio:9000
s3Credentials:
accessKeyId:
name: minio-creds
key: ACCESS_KEY_ID
secretAccessKey:
name: minio-creds
key: ACCESS_SECRET_KEY
wal:
compression: gzip
retentionPolicy: "1d"
EOF
Cluster configuration is:
tee $cluster_name.yaml << EOF
apiVersion: postgresql.cnpg.io/v1
kind: Cluster
metadata:
name: $cluster_name
spec:
instances: 3
imageName: $cnpg_image_name
storage:
size: 1Gi
plugins:
- name: barman-cloud.cloudnative-pg.io
isWALArchiver: true
parameters:
barmanObjectName: minio-store
EOF
The output of the command kubectl cnpg status $cluster_name shows Continuous Backup status Not configured:
[alexey@wsl2 ~]$ kubectl cnpg status $cluster_name
Cluster Summary
Name default/cluster-barman-cloud-cnpg
System ID: 7551820857236926487
PostgreSQL Image: ghcr.io/cloudnative-pg/postgresql:17.6
Primary instance: cluster-barman-cloud-cnpg-1
Primary start time: 2025-09-19 15:22:08 +0000 UTC (uptime 1h30m57s)
Status: Cluster in healthy state
Instances: 3
Ready instances: 3
Size: 143M
Current Write LSN: 0/8000000 (Timeline: 1 - WAL File: 000000010000000000000008)
Continuous Backup status
Not configured
Streaming Replication status
Replication Slots Enabled
Name Sent LSN Write LSN Flush LSN Replay LSN Write Lag Flush Lag Replay Lag State Sync State Sync Priority Replication Slot
---- -------- --------- --------- ---------- --------- --------- ---------- ----- ---------- ------------- ----------------
cluster-barman-cloud-cnpg-2 0/8000000 0/8000000 0/8000000 0/8000000 00:00:00 00:00:00 00:00:00 streaming async 0 active
cluster-barman-cloud-cnpg-3 0/8000000 0/8000000 0/8000000 0/8000000 00:00:00 00:00:00 00:00:00 streaming async 0 active
Instances status
Name Current LSN Replication role Status QoS Manager Version Node
---- ----------- ---------------- ------ --- --------------- ----
cluster-barman-cloud-cnpg-1 0/8000000 Primary OK BestEffort 1.27.0 minikube
cluster-barman-cloud-cnpg-2 0/8000000 Standby (async) OK BestEffort 1.27.0 minikube
cluster-barman-cloud-cnpg-3 0/8000000 Standby (async) OK BestEffort 1.27.0 minikube
Plugins status
Name Version Status Reported Operator Capabilities
---- ------- ------ ------------------------------
barman-cloud.cloudnative-pg.io 0.6.0 N/A Reconciler Hooks, Lifecycle Service
which was not the case with native barman setup.
What is wrong with my plugin barman setup ?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working