Compare commits

...

2 Commits

Author SHA1 Message Date
Max Eisner
4f53d48aa6
Merge 78d02d6803 into 367db3cd66 2025-12-05 11:15:09 -05:00
Max Eisner
78d02d6803
docs: add IRSA instructions
Signed-off-by: Max Eisner <4730112+max-ae@users.noreply.github.com>
2025-08-18 13:36:01 +02:00
2 changed files with 17 additions and 0 deletions

View File

@ -103,6 +103,10 @@ As you can see, the contents of `barmanObjectStore` have been copied directly
under the `configuration` field of the `ObjectStore` resource, using the same
secret references.
### IAM Role for Service Account (IRSA)
If you use IRSA, you need to configure the `ObjectStore` to utilize the correct role as described in the [`Object Store Reference`](object_stores.md#iam-role-for-service-account-irsa).
## Step 2: Update the `Cluster` for plugin WAL archiving
Once the `ObjectStore` resource is in place, update the `Cluster` resource as

View File

@ -101,6 +101,19 @@ spec:
[...]
```
In addition, configure the `ObjectStore` to inherit permissions from the IAM role referenced in the service account:
```yaml
apiVersion: barmancloud.cnpg.io/v1
kind: ObjectStore
metadata:
[...]
spec:
configuration:
s3Credentials:
inheritFromIAMRole: true
```
### S3 Lifecycle Policy
Barman Cloud uploads backup files to S3 but does not modify or delete them afterward.