Replies: 1 comment
-
Your understanding seems correct to me from the available fields in the connectionDetails array. Would this existing issue accurately cover your use case? #3070 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I am trying to set up S3-Storage for Thanos. I did already build a composite resource that builds the required S3-Bucket with IAM-Credentials/-policy, Bucket, KMS-Key, writing everything required to the connectionSecret.
Unfortunately, Thanos components expect the credentials to be in a single Secret value containing the configuration yaml required for accessing the bucket. e.g.:
As far as I understand the documentation values for the connection Secret can either be copied from a field path, another connection Secret or given as static value.
Can transformations also be applied for the connectionSecret fields by
combine
(already using it for generating the IAM policy) without exposing the access keys by combining to a field in the composite resource?Beta Was this translation helpful? Give feedback.
All reactions