Commit Graph

18 Commits

Author SHA1 Message Date
Lili Cosic
d04ddf5a98 manifests: Regenerate files 2019-09-12 17:54:45 +02:00
Lili Cosic
c34bbb21e5 manifests: Regenerate files 2019-08-30 18:17:27 +02:00
Josh Tilles
5d7154cea5 Fix prometheus-operator’s git sha to use v0.30.0
Fixes [#105](https://github.com/coreos/kube-prometheus/issues/105)
2019-06-10 14:06:50 -04:00
Matthias Loibl
d9bb0c2ec4 Update Prometheus Operator in kube-prometheus to v0.29.0 2019-02-20 12:46:39 +01:00
Frederic Branczyk
31bb1a9353 *: re-generate kube-prometheus 2019-01-08 16:18:57 +01:00
Sergiusz Urbaniak
fc65336082 kube-prometheus: regenerate 2018-11-30 14:28:45 +01:00
Frederic Branczyk
830500cfc7 kube-prometheus: Re-generate 2018-10-25 13:24:37 +02:00
Matthias Loibl
e2476ce2ef contrib/kube-prometheus: Generate new manifests and docs with prom operator v0.24 2018-10-12 14:01:54 +02:00
Frederic Branczyk
159eb05497 kube-prometheus: Update dependencies 2018-08-13 15:21:00 +02:00
Frederic Branczyk
9a011bb8ac kube-prometheus: Use locking mechanism for jsonnet dependencies 2018-07-25 17:21:50 +02:00
Lucas Serven
d1cd951903 *: regenerate 2018-07-23 13:28:14 +02:00
Frederic Branczyk
9ec8ae65ee *: Allow settings custom tags of container images 2018-07-09 13:23:00 +02:00
Frederic Branczyk
9c26600e0a *: Fix CRD generation 2018-07-02 16:54:56 +02:00
Frederic Branczyk
171b7c41e1 *: Re-generate 2018-07-02 10:54:27 +02:00
Tamal Saha
0de5a5c8cd Update client libraries to Kubernetes 1.11 2018-07-01 09:23:00 -07:00
Max Leonard Inden
453e170f6a prometheus: Enable live migration of rule configmaps to rule file crds
With this patch the Prometheus Operator checks if there are any
Kubernetes ConfigMaps inside the Prometheus namespace which fullfill the
`Spec.RuleSelector` requirement. If so, it creates a RuleFile for each
key in the `ConfigMap.Spec.Data` map inside the Prometheus namespace.
2018-05-31 10:47:50 +02:00
Max Leonard Inden
9e180452f8 prometheus: Introduce RuleFile Custom Resource Definition
This patch introduces a new Custom Resource Definition to the
Prometheus Operator - the Rule CRD. It addresses two main
needs:

1. Prometheus (alerting and recording) Rule validation during creation time
via Kubernetes Custom Resource Definition validation.

2. Life-cycle management of Prometheus application Rules alongside the
application itself, inside the applications Kubernetes namespace, not
necessarily the namespace of the scraping Prometheus instance.

A user defines Prometheus alerting and recording Rules via a Kubernetes
Custom Resource Definition. These Custom Resource Definitions can be
fully validated by the Kubernetes API server during creation time via
automatically generated OpenAPI specifications. Instead of the
restriction of a Prometheus instance to only select Rule definitions
inside its own namespace, the Prometheus specification is extended to
also specify namespaces to look for Rule Custom Resource Definitions
outside its own namespace.

---

Dependent technical changes:

- prometheus: Use github.com/jimmidyson/configmap-reload to reload rules

- prometheus: Remove Prometheus Statefulset deletion function. Starting
with K8s >=1.8 this is handled via OwnerReferences.

- prometheus: Do not add rule files checksum to Prometheus configuration
secret

- prometheus: Update StatefulSet only on relevant changes. Instead of
updating the Prometheus StatefulSet on every `sync()` run, only update
it if the input parameters to `makeStatefulSet` change.  Enforce this
via a checksum of the parameters which is saved inside the annotations
of the statefulset.

- e2e/prometheus: Check how often resources (Secret, ConfigMap,
Prometheus CRD, Service) are updated to enforce that Prometheus Operator
only updated created resources if necessary.

- contrib/prometheus-config-reloader: Remove logic to retriev K8s
ConfigMaps. These are mounted into the pod right away now.
2018-05-18 16:27:20 +02:00
Frederic Branczyk
3388f96afe Address comments 2018-05-06 08:29:52 -07:00