Skip to content

Conversation

@abelfodil
Copy link
Contributor

What this PR does / why we need it

Pass through Thanos configuration instead of recreating every field manually. This would stabilize the feature as it would follow https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/api-reference/api.md#thanosspec 1:1.

Which issue this PR fixes

None

Special notes for your reviewer

Checklist

  • DCO signed
  • Chart Version bumped
  • Title of the PR starts with chart name (e.g. [prometheus-couchdb-exporter])

@jkroepke
Copy link
Member

Hm, it feels like just breaking things. (No Secret anymore)

@abelfodil
Copy link
Contributor Author

I don't see the need of defining the secret through the chart. It's not an object from CRD, so people can define theirs separately and reference it. If people really want to define a secret through the chart, they can use extraSecret and reference it in Thanos sidecar spec.

While it does break things indeed, it also opens more opportunities for customization.

@jkroepke
Copy link
Member

Hm. I say that more opportunities are possible, without breaking existing things.

Copy link
Member

@jkroepke jkroepke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please add some backwards compatibility.

@abelfodil
Copy link
Contributor Author

Ack

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants