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
Bump v0.36.0 #54
Bump v0.36.0 #54
Conversation
OWNERS: add krasi-georgiev and paulfantom
Currently when passing `--config-reloader-(cpu|memory)` values those are used only for limits. This PR sets the same values for requests. I wasn't sure if the options for the requests should have been passed with separate options but I thought this was a good compromise in the meantime. The initial question was brought up in prometheus-operator/kube-prometheus#376
As discussed in prometheus-operator#2938 the binary name `lint` is too generic if used outside of the docker image. So it's been renamed to `po-lint`.
…ader-requests prometheus-operator: set config-reloader containers resources
…_to_po-lint rename `lint` to `po-lint`
…tation Update Exposing Prometheus and Alertmanager documentation
This change adds a new kubernetes CustomResourceDefinition and associated operator/controller for ThanosRuler instances. This allows ThanosRuler instances to be deployed according to the configuration in the ThanosRuler objects. A rule selector can be used to select PrometheusRule objects which are combined into a ConfigMap and mounted into the associated ThanosRuler pod. Co-authored-by: Matthias Loibl <mail@matthiasloibl.com> Co-authored-by: Sergiusz Urbaniak <sergiusz.urbaniak@gmail.com>
add thanos-ruler operator
* bump golang to 1.13 * bump promtool to 2.15.2 * lock jsonnet-bundler on version 0.2.0 * add po-lint build
Tooling image updates
Currently, prometheus-operator has access to all verbs to all custom resources. This fixes it by limiting it to custom resources under its jurisdiction.
jsonnet/prometheus-operator: restrict api extension RBAC rules
scripts/tooling: fix jsonnet version variable by removing 'v' prefix where needed.
… prometheus-operator-lint image
Instead of printing deprecation warnings on every sync, only warn when a resource is added or updated.
Signed-off-by: yeya24 <yb532204897@gmail.com>
Add basic rules test for thanos. Fix e2e test to call thanos e2e test.
Switch tooling image
…nter support basic additional printer columns
Signed-off-by: yeya24 <yb532204897@gmail.com>
…able Bump thanos reloader package
Signed-off-by: yeya24 <yb532204897@gmail.com>
Changes in kubernetes v1.17 cause an endless update loop due to validation errors cause by setting the 'apiVersion' and 'kind' fields in the StatefulSet spec. These two fields are set to empty strings by the Kube API server, and v1.17 added validation that does not allow these fields to be modified. See prometheus-operator#2950
…date-loop prevent prometheus sts update loop
Signed-off-by: yeya24 <yb532204897@gmail.com>
Support thanos ruler replica label
jsonnet bundler v0.2.0 no longer accepts a local path to a git repository.
…t-bundler Upgrade jsonnet bundler
Prometheus image should default to latest version in compatibility matrix. Also updates Alertmanager and Thanos to latest stable versions.
The allowed-tls-file and denied-tls-file tests of service monitor config were not able to access tls certificate files on the local filesystem. This issue was only exposed when updating the default Prometheus version above 2.8.0 because this version introduced validation of the TLS config. This changes the config for these two tests to mount a secret containing these two files.
Signed-off-by: yeya24 <yb532204897@gmail.com>
Signed-off-by: yeya24 <yb532204897@gmail.com>
Signed-off-by: yeya24 <yb532204897@gmail.com>
…t-prometheus-alertmanager-thanos-versions update default image versions
Update comments from prometheus to thanos ruler
…p-labels Fix thanos ruler alert drop labels
/test e2e-aws |
/test e2e-aws |
/test e2e-aws |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pgier, s-urbaniak 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 |
No description provided.