[bot] [main] Automated version update (#2451)
Co-authored-by: Prometheus Operator Bot <prom-op-bot@users.noreply.github.com>
This commit is contained in:
@@ -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: alertmanagers.monitoring.coreos.com
|
||||
spec:
|
||||
group: monitoring.coreos.com
|
||||
@@ -48,7 +48,14 @@ spec:
|
||||
name: v1
|
||||
schema:
|
||||
openAPIV3Schema:
|
||||
description: Alertmanager describes an Alertmanager cluster.
|
||||
description: |-
|
||||
The `Alertmanager` custom resource definition (CRD) defines a desired [Alertmanager](https://prometheus.io/docs/alerting) setup to run in a Kubernetes cluster. It allows to specify many options such as the number of replicas, persistent storage and many more.
|
||||
|
||||
|
||||
For each `Alertmanager` resource, the Operator deploys a `StatefulSet` in the same namespace. When there are two or more configured replicas, the Operator runs the Alertmanager instances in high-availability mode.
|
||||
|
||||
|
||||
The resource defines via label and namespace selectors which `AlertmanagerConfig` objects should be associated to the deployed Alertmanager instances.
|
||||
properties:
|
||||
apiVersion:
|
||||
description: |-
|
||||
|
||||
Reference in New Issue
Block a user