Skip to content
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

Merged
merged 15 commits into from Mar 11, 2020

Conversation

lilic
Copy link

@lilic lilic commented Mar 11, 2020

cc @pgier

jalev and others added 14 commits March 5, 2020 17:23
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.
…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
@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 11, 2020
@openshift-ci-robot openshift-ci-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Mar 11, 2020
@lilic
Copy link
Author

lilic commented Mar 11, 2020

/hold

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 11, 2020
@lilic
Copy link
Author

lilic commented Mar 11, 2020

/hold cancel

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 11, 2020
@pgier
Copy link

pgier commented Mar 11, 2020

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Mar 11, 2020
@openshift-ci-robot
Copy link

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

@pgier
Copy link

pgier commented Mar 11, 2020

/hold

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 11, 2020
@openshift-merge-robot openshift-merge-robot merged commit 18ee5fa into openshift:master Mar 11, 2020
@lilic lilic deleted the update-prom-operator branch March 11, 2020 16:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

9 participants