Hi Percona team,
We are running Percona Server for MongoDB Operator with PMM enabled. PMM is successfully showing backup activity/status in dashboards, so it can observe backups created by the operator/PBM.
The gap is that the PMM Backup & Restore UI still requires manual storage configuration before backups can be managed from the UI. In our Kubernetes setup, backup storage is already configured declaratively in the PerconaServerMongoDB resource:
spec:
backup:
enabled: true
pitr:
enabled: true
storages:
<storage-name>:
type: s3
s3:
bucket: <bucket>
region: <region>
tasks:
- name: daily
enabled: true
storageName: <storage-name>
The pods use Kubernetes/IAM integration for S3 access, not static AWS access key / secret key credentials.
What is the recommended way to make PMM Backup & Restore use or import the operator/PBM backup storage configuration so the UI can manage backups without manually reconfiguring storage?
If this is not currently supported, would Percona consider supporting one of these options?
- PMM reads/imports PBM storage configuration already managed by the Percona MongoDB Operator.
- PMM Backup & Restore supports Kubernetes/IAM/IRSA-style credentials instead of requiring static S3 access key and secret key.
- PMM exposes a declarative/API-driven way to configure Backup & Restore storage from Kubernetes manifests, so it can be automated alongside the operator deployment.
The desired outcome is: backups remain configured in Git/Kubernetes, PMM can still manage backup/restore workflows from the UI, and no static cloud credentials need to be entered manually.