New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bring in new commits from master #57
Bring in new commits from master #57
Conversation
Instead of hardcoding each name of each configmap of the rules that are generated, instead use a glob on the configmap name. This means we can have 0 or more instances of rules existing, and won't make the ThanosRuler StatefulSet object force a restart when a large number of rules are created.
When a PrometheusRule object is created the Thanos Ruler statefulset object is touched for update. The previous behaviour updated the statefulset regardless if it actually needed an update. This update creates a 'diff' check to see whether or not the statefulset needs to be updated, basically the same way that it is defined in the prometheus/operator. We also force a hash key to be generated on the first go.
update thanos to v0.11.0
…ule-cmd-generation Fix constant Thanos Ruler Statefulset generation
This allows TLS config using the 'query.config' CLI arg to thanos ruler.
…er-to-querier pkg/thanos: add queryConfig to ThanosRuler spec
Now it is more clear that `port` is name of port from the service, while targetPort is the name of port from the target pod.
The 'thanos rule' command allows multiple alertmanagers.url args to be specified, so this changes the ThanosRuler custom resource spec to match.
Clarify that Endpoint.targetPort is pod port
…e-alertmanager-urls pkg/thanos: allow multiple alertmanager urls to be specified
* pkg/thanos: add grpc-server-tls config * pkg/prometheus: add grpc-server-tls config to thanos sidecar * update generated files for thanos grpc tls config
03efed1
to
fcb7381
Compare
/hold |
/hold cancel |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lilic, pgier The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/hold |
cc @pgier