FEAT(velero): configure minio

- for selective velero backup
Added pod annotation to exclude PVC data from Velero backups while
preserving MinIO resource definitions:
- backup.velero.io/backup-volumes-excludes: export

This prevents circular backup of the velero-backups bucket while
still backing up MinIO StatefulSet, Services, and configuration.

Note: MinIO bucket data (bucket, bucket-dev, velero-backups) will
NOT be backed up. Consider separate backup strategy for critical
bucket data if needed.

minio/helm-values/minio.yaml

@@ -65,6 +65,12 @@ consoleIngress:
 # This prevents Kubernetes from injecting service-related environment variables
 enableServiceLinks: false
 
+# Pod annotations for Velero backup exclusion
+# Exclude PVC data from backup (prevent circular backup of velero-backups bucket)
+# MinIO resources (StatefulSet, Service, etc.) will still be backed up
+podAnnotations:
+  backup.velero.io/backup-volumes-excludes: export
+
 # Use soft anti-affinity since worker-1 needs 2 pods (has 2 disks)
 affinity:
   podAntiAffinity:

velero/helm-values/velero.yaml

@@ -92,7 +92,9 @@ schedules:
         # Non-essential namespaces (to save storage)
         - postgresql-dev  # Dev database not needed in disaster recovery
         - harbor          # Rebuildable container images
-        - minio           # Backup storage itself (prevents circular backup)
+        # Note: minio namespace is now included in backup
+        # MinIO PVC data is excluded via pod annotation (backup.velero.io/backup-volumes-excludes)
+        # This backs up MinIO resources but not the data (prevents circular backup)
       snapshotVolumes: true
       defaultVolumesToFsBackup: true