easylinux/kube-prometheus
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[bot] [main] Automated version update (#2451)

Browse Source 
Co-authored-by: Prometheus Operator Bot <prom-op-bot@users.noreply.github.com>
This commit is contained in:
PromOperatorBot
2024-07-08 19:29:23 +02:00
committed by GitHub
parent b5b59bc0b4
commit d141b7cc9a
30 changed files with 558 additions and 99 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
manifests/setup/0prometheusCustomResourceDefinition.yaml
View File

@@ -3,7 +3,7 @@ kind: CustomResourceDefinition
metadata:
annotations:
controller-gen.kubebuilder.io/version: v0.15.0
operator.prometheus.io/version: 0.74.0
operator.prometheus.io/version: 0.75.1
name: prometheuses.monitoring.coreos.com
spec:
group: monitoring.coreos.com
@@ -48,7 +48,17 @@ spec:
name: v1
schema:
openAPIV3Schema:
description: Prometheus defines a Prometheus deployment.
description: |-
The `Prometheus` custom resource definition (CRD) defines a desired [Prometheus](https://prometheus.io/docs/prometheus) setup to run in a Kubernetes cluster. It allows to specify many options such as the number of replicas, persistent storage, and Alertmanagers where firing alerts should be sent and many more.
For each `Prometheus` resource, the Operator deploys one or several `StatefulSet` objects in the same namespace. The number of StatefulSets is equal to the number of shards which is 1 by default.
The resource defines via label and namespace selectors which `ServiceMonitor`, `PodMonitor`, `Probe` and `PrometheusRule` objects should be associated to the deployed Prometheus instances.
The Operator continuously reconciles the scrape and rules configuration and a sidecar container running in the Prometheus pods triggers a reload of the configuration when needed.
properties:
apiVersion:
description: |-