[bot] [main] Automated version update
This commit is contained in:
Prometheus Operator Bot
@@ -2,7 +2,7 @@ apiVersion: apiextensions.k8s.io/v1
|
||||
kind: CustomResourceDefinition
|
||||
metadata:
|
||||
annotations:
|
||||
controller-gen.kubebuilder.io/version: v0.6.2
|
||||
controller-gen.kubebuilder.io/version: v0.8.0
|
||||
creationTimestamp: null
|
||||
name: prometheuses.monitoring.coreos.com
|
||||
spec:
|
||||
@@ -2678,6 +2678,7 @@ spec:
|
||||
monitors and probes. This is an experimental feature, this behaviour
|
||||
could change or be removed in the future. Only valid in Prometheus
|
||||
versions 2.28.0 and newer.'
|
||||
pattern: (^0|([0-9]*[.])?[0-9]+((K|M|G|T|E|P)i?)?B)$
|
||||
type: string
|
||||
enforcedLabelLimit:
|
||||
description: Per-scrape limit on number of labels that will be accepted
|
||||
@@ -2704,8 +2705,8 @@ spec:
|
||||
description: "EnforcedNamespaceLabel If set, a label will be added
|
||||
to \n 1. all user-metrics (created by `ServiceMonitor`, `PodMonitor`
|
||||
and `Probe` objects) and 2. in all `PrometheusRule` objects (except
|
||||
the ones excluded in `prometheusRulesExcludedFromEnforce`) to *
|
||||
alerting & recording rules and * the metrics used in their expressions
|
||||
the ones excluded in `prometheusRulesExcludedFromEnforce`) to *
|
||||
alerting & recording rules and * the metrics used in their expressions
|
||||
(`expr`). \n Label name is this field's value. Label value is the
|
||||
namespace of the created object (mentioned above)."
|
||||
type: string
|
||||
@@ -2732,6 +2733,42 @@ spec:
|
||||
evaluationInterval:
|
||||
description: 'Interval between consecutive evaluations. Default: `1m`'
|
||||
type: string
|
||||
excludedFromEnforcement:
|
||||
description: List of references to PodMonitor, ServiceMonitor, Probe
|
||||
and PrometheusRule objects to be excluded from enforcing a namespace
|
||||
label of origin. Applies only if enforcedNamespaceLabel set to true.
|
||||
items:
|
||||
description: ObjectReference references a PodMonitor, ServiceMonitor,
|
||||
Probe or PrometheusRule object.
|
||||
properties:
|
||||
group:
|
||||
default: monitoring.coreos.com
|
||||
description: Group of the referent. When not specified, it defaults
|
||||
to `monitoring.coreos.com`
|
||||
enum:
|
||||
- monitoring.coreos.com
|
||||
type: string
|
||||
name:
|
||||
description: Name of the referent. When not set, all resources
|
||||
are matched.
|
||||
type: string
|
||||
namespace:
|
||||
description: 'Namespace of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/'
|
||||
minLength: 1
|
||||
type: string
|
||||
resource:
|
||||
description: Resource of the referent.
|
||||
enum:
|
||||
- prometheusrules
|
||||
- servicemonitors
|
||||
- podmonitors
|
||||
- probes
|
||||
type: string
|
||||
required:
|
||||
- namespace
|
||||
- resource
|
||||
type: object
|
||||
type: array
|
||||
externalLabels:
|
||||
additionalProperties:
|
||||
type: string
|
||||
@@ -4265,10 +4302,11 @@ spec:
|
||||
will _not_ be added when value is set to empty string (`""`).
|
||||
type: string
|
||||
prometheusRulesExcludedFromEnforce:
|
||||
description: PrometheusRulesExcludedFromEnforce - list of prometheus
|
||||
description: 'PrometheusRulesExcludedFromEnforce - list of prometheus
|
||||
rules to be excluded from enforcing of adding namespace labels.
|
||||
Works only if enforcedNamespaceLabel set to true. Make sure both
|
||||
ruleNamespace and ruleName are set for each pair
|
||||
ruleNamespace and ruleName are set for each pair. Deprecated: use
|
||||
excludedFromEnforcement instead.'
|
||||
items:
|
||||
description: PrometheusRuleExcludeConfig enables users to configure
|
||||
excluded PrometheusRule names and their namespaces to be ignored
|
||||
@@ -5192,8 +5230,8 @@ spec:
|
||||
hours days weeks years).
|
||||
type: string
|
||||
retentionSize:
|
||||
description: 'Maximum amount of disk space used by blocks. Supported
|
||||
units: B, KB, MB, GB, TB, PB, EB. Ex: `512MB`.'
|
||||
description: Maximum amount of disk space used by blocks.
|
||||
pattern: (^0|([0-9]*[.])?[0-9]+((K|M|G|T|E|P)i?)?B)$
|
||||
type: string
|
||||
routePrefix:
|
||||
description: The route prefix Prometheus registers HTTP handlers for.
|
||||
@@ -5731,13 +5769,13 @@ spec:
|
||||
automatically if one of them is empty and the other
|
||||
is non-empty. There are two important differences
|
||||
between DataSource and DataSourceRef: * While DataSource
|
||||
only allows two specific types of objects, DataSourceRef allows
|
||||
any non-core object, as well as PersistentVolumeClaim
|
||||
only allows two specific types of objects, DataSourceRef
|
||||
allows any non-core object, as well as PersistentVolumeClaim
|
||||
objects. * While DataSource ignores disallowed values
|
||||
(dropping them), DataSourceRef preserves all values,
|
||||
and generates an error if a disallowed value is specified.
|
||||
(Alpha) Using this field requires the AnyVolumeDataSource
|
||||
feature gate to be enabled.'
|
||||
(dropping them), DataSourceRef preserves all values,
|
||||
and generates an error if a disallowed value is
|
||||
specified. (Alpha) Using this field requires the
|
||||
AnyVolumeDataSource feature gate to be enabled.'
|
||||
properties:
|
||||
apiGroup:
|
||||
description: APIGroup is the group for the resource
|
||||
@@ -5954,11 +5992,11 @@ spec:
|
||||
and the other is non-empty. There are two important
|
||||
differences between DataSource and DataSourceRef: *
|
||||
While DataSource only allows two specific types of objects,
|
||||
DataSourceRef allows any non-core object, as well
|
||||
as PersistentVolumeClaim objects. * While DataSource
|
||||
ignores disallowed values (dropping them), DataSourceRef preserves
|
||||
DataSourceRef allows any non-core object, as well as
|
||||
PersistentVolumeClaim objects. * While DataSource ignores
|
||||
disallowed values (dropping them), DataSourceRef preserves
|
||||
all values, and generates an error if a disallowed value
|
||||
is specified. (Alpha) Using this field requires the
|
||||
is specified. (Alpha) Using this field requires the
|
||||
AnyVolumeDataSource feature gate to be enabled.'
|
||||
properties:
|
||||
apiGroup:
|
||||
@@ -6603,10 +6641,10 @@ spec:
|
||||
description: 'WhenUnsatisfiable indicates how to deal with a
|
||||
pod if it doesn''t satisfy the spread constraint. - DoNotSchedule
|
||||
(default) tells the scheduler not to schedule it. - ScheduleAnyway
|
||||
tells the scheduler to schedule the pod in any location, but
|
||||
tells the scheduler to schedule the pod in any location, but
|
||||
giving higher precedence to topologies that would help reduce
|
||||
the skew. A constraint is considered "Unsatisfiable" for
|
||||
an incoming pod if and only if every possible node assignment
|
||||
the skew. A constraint is considered "Unsatisfiable" for an
|
||||
incoming pod if and only if every possible node assignment
|
||||
for that pod would violate "MaxSkew" on some topology. For
|
||||
example, in a 3-zone cluster, MaxSkew is set to 1, and pods
|
||||
with the same labelSelector spread as 3/1/1: | zone1 | zone2
|
||||
@@ -7058,18 +7096,17 @@ spec:
|
||||
pod starts, and deleted when the pod is removed. \n Use this
|
||||
if: a) the volume is only needed while the pod runs, b) features
|
||||
of normal volumes like restoring from snapshot or capacity
|
||||
\ tracking are needed, c) the storage driver is specified
|
||||
through a storage class, and d) the storage driver supports
|
||||
dynamic volume provisioning through a PersistentVolumeClaim
|
||||
(see EphemeralVolumeSource for more information on the
|
||||
connection between this volume type and PersistentVolumeClaim).
|
||||
\n Use PersistentVolumeClaim or one of the vendor-specific
|
||||
APIs for volumes that persist for longer than the lifecycle
|
||||
of an individual pod. \n Use CSI for light-weight local ephemeral
|
||||
volumes if the CSI driver is meant to be used that way - see
|
||||
the documentation of the driver for more information. \n A
|
||||
pod can use both types of ephemeral volumes and persistent
|
||||
volumes at the same time."
|
||||
tracking are needed, c) the storage driver is specified through
|
||||
a storage class, and d) the storage driver supports dynamic
|
||||
volume provisioning through a PersistentVolumeClaim (see EphemeralVolumeSource
|
||||
for more information on the connection between this volume
|
||||
type and PersistentVolumeClaim). \n Use PersistentVolumeClaim
|
||||
or one of the vendor-specific APIs for volumes that persist
|
||||
for longer than the lifecycle of an individual pod. \n Use
|
||||
CSI for light-weight local ephemeral volumes if the CSI driver
|
||||
is meant to be used that way - see the documentation of the
|
||||
driver for more information. \n A pod can use both types of
|
||||
ephemeral volumes and persistent volumes at the same time."
|
||||
properties:
|
||||
volumeClaimTemplate:
|
||||
description: "Will be used to create a stand-alone PVC to
|
||||
@@ -7157,13 +7194,13 @@ spec:
|
||||
other is non-empty. There are two important differences
|
||||
between DataSource and DataSourceRef: * While
|
||||
DataSource only allows two specific types of objects,
|
||||
DataSourceRef allows any non-core object, as
|
||||
well as PersistentVolumeClaim objects. * While
|
||||
DataSource ignores disallowed values (dropping
|
||||
them), DataSourceRef preserves all values, and
|
||||
generates an error if a disallowed value is specified.
|
||||
(Alpha) Using this field requires the AnyVolumeDataSource
|
||||
feature gate to be enabled.'
|
||||
DataSourceRef allows any non-core object, as well
|
||||
as PersistentVolumeClaim objects. * While DataSource
|
||||
ignores disallowed values (dropping them), DataSourceRef
|
||||
preserves all values, and generates an error if
|
||||
a disallowed value is specified. (Alpha) Using
|
||||
this field requires the AnyVolumeDataSource feature
|
||||
gate to be enabled.'
|
||||
properties:
|
||||
apiGroup:
|
||||
description: APIGroup is the group for the resource
|
||||
|
||||
Reference in New Issue
Block a user