I'm very new to all of this so sorry if this just seems completely pointless.
I'd like to use the barman cloud CNPG-I plugin on my Kubernetes cluster that uses Ceph/Rook for its S3 object store. With Ceph, buckets are defined with a ObjectBucketClaim and the names are typically generated based on some prefix. This ends up creating a Secret for credentials and endpoint and bucket name information in a ConfigMap. The endpoint is predictable/static so it isn't a huge deal to hardcode that in barman, but the bucket name is unique. So if I said the bucket name prefix is "mybucket" then I might get "mybucket-a29713fe-61a3-4132-84df-4866f28600f4".
I'm wondering if it would be possible to pull the DestinationPath in BarmanObjectStoreConfiguration from a ConfigMap? Actually, I'm realizing now that this is even harder than I thought as the DestinationPath includes the S3 sub-path and the s3:// protocol prefix. Regardless, what are your thoughts?
I'm very new to all of this so sorry if this just seems completely pointless.
I'd like to use the barman cloud CNPG-I plugin on my Kubernetes cluster that uses Ceph/Rook for its S3 object store. With Ceph, buckets are defined with a
ObjectBucketClaimand the names are typically generated based on some prefix. This ends up creating a Secret for credentials and endpoint and bucket name information in a ConfigMap. The endpoint is predictable/static so it isn't a huge deal to hardcode that in barman, but the bucket name is unique. So if I said the bucket name prefix is "mybucket" then I might get "mybucket-a29713fe-61a3-4132-84df-4866f28600f4".I'm wondering if it would be possible to pull the
DestinationPathinBarmanObjectStoreConfigurationfrom aConfigMap? Actually, I'm realizing now that this is even harder than I thought as theDestinationPathincludes the S3 sub-path and thes3://protocol prefix. Regardless, what are your thoughts?