---
apiVersion: apiextensions.k8s.io/v1
kind: CustomResourceDefinition
metadata:
  annotations:
    api-approved.openshift.io: https://github.com/openshift/api/pull/1406
    api.openshift.io/merged-by-featuregates: "true"
    description: OpenShift Monitoring alerting rules
    include.release.openshift.io/hypershift: "true"
    include.release.openshift.io/ibm-cloud-managed: "true"
    include.release.openshift.io/self-managed-high-availability: "true"
    include.release.openshift.io/single-node-developer: "true"
  creationTimestamp: "2025-10-27T11:18:18Z"
  generation: 1
  labels:
    app.kubernetes.io/managed-by: cluster-version-operator
    app.kubernetes.io/part-of: openshift-monitoring
  managedFields:
  - apiVersion: apiextensions.k8s.io/v1
    fieldsType: FieldsV1
    fieldsV1:
      f:metadata:
        f:annotations:
          .: {}
          f:api-approved.openshift.io: {}
          f:api.openshift.io/merged-by-featuregates: {}
          f:description: {}
          f:include.release.openshift.io/hypershift: {}
          f:include.release.openshift.io/ibm-cloud-managed: {}
          f:include.release.openshift.io/self-managed-high-availability: {}
          f:include.release.openshift.io/single-node-developer: {}
        f:labels:
          .: {}
          f:app.kubernetes.io/managed-by: {}
          f:app.kubernetes.io/part-of: {}
        f:ownerReferences:
          .: {}
          k:{"uid":"d36bdf59-d268-4238-afb0-5e0b21cca1a4"}: {}
      f:spec:
        f:conversion:
          .: {}
          f:strategy: {}
        f:group: {}
        f:names:
          f:kind: {}
          f:listKind: {}
          f:plural: {}
          f:singular: {}
        f:scope: {}
        f:versions: {}
    manager: cluster-version-operator
    operation: Update
    time: "2025-10-27T11:18:18Z"
  - apiVersion: apiextensions.k8s.io/v1
    fieldsType: FieldsV1
    fieldsV1:
      f:status:
        f:acceptedNames:
          f:kind: {}
          f:listKind: {}
          f:plural: {}
          f:singular: {}
        f:conditions:
          k:{"type":"Established"}:
            .: {}
            f:lastTransitionTime: {}
            f:message: {}
            f:reason: {}
            f:status: {}
            f:type: {}
          k:{"type":"NamesAccepted"}:
            .: {}
            f:lastTransitionTime: {}
            f:message: {}
            f:reason: {}
            f:status: {}
            f:type: {}
    manager: kube-apiserver
    operation: Update
    subresource: status
    time: "2025-10-27T11:18:18Z"
  name: alertingrules.monitoring.openshift.io
  ownerReferences:
  - apiVersion: config.openshift.io/v1
    controller: true
    kind: ClusterVersion
    name: version
    uid: d36bdf59-d268-4238-afb0-5e0b21cca1a4
  resourceVersion: "931"
  uid: 35d40775-6a82-4e4a-8d7f-0d5cde7f9d43
spec:
  conversion:
    strategy: None
  group: monitoring.openshift.io
  names:
    kind: AlertingRule
    listKind: AlertingRuleList
    plural: alertingrules
    singular: alertingrule
  scope: Namespaced
  versions:
  - name: v1
    schema:
      openAPIV3Schema:
        description: |-
          AlertingRule represents a set of user-defined Prometheus rule groups containing
          alerting rules.  This resource is the supported method for cluster admins to
          create alerts based on metrics recorded by the platform monitoring stack in
          OpenShift, i.e. the Prometheus instance deployed to the openshift-monitoring
          namespace.  You might use this to create custom alerting rules not shipped with
          OpenShift based on metrics from components such as the node_exporter, which
          provides machine-level metrics such as CPU usage, or kube-state-metrics, which
          provides metrics on Kubernetes usage.

          The API is mostly compatible with the upstream PrometheusRule type from the
          prometheus-operator.  The primary difference being that recording rules are not
          allowed here -- only alerting rules.  For each AlertingRule resource created, a
          corresponding PrometheusRule will be created in the openshift-monitoring
          namespace.  OpenShift requires admins to use the AlertingRule resource rather
          than the upstream type in order to allow better OpenShift specific defaulting
          and validation, while not modifying the upstream APIs directly.

          You can find upstream API documentation for PrometheusRule resources here:

          https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/api.md

          Compatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer).
        properties:
          apiVersion:
            description: |-
              APIVersion defines the versioned schema of this representation of an object.
              Servers should convert recognized schemas to the latest internal value, and
              may reject unrecognized values.
              More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources
            type: string
          kind:
            description: |-
              Kind is a string value representing the REST resource this object represents.
              Servers may infer this from the endpoint the client submits requests to.
              Cannot be updated.
              In CamelCase.
              More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
            type: string
          metadata:
            type: object
          spec:
            description: spec describes the desired state of this AlertingRule object.
            properties:
              groups:
                description: |-
                  groups is a list of grouped alerting rules.  Rule groups are the unit at
                  which Prometheus parallelizes rule processing.  All rules in a single group
                  share a configured evaluation interval.  All rules in the group will be
                  processed together on this interval, sequentially, and all rules will be
                  processed.

                  It's common to group related alerting rules into a single AlertingRule
                  resources, and within that resource, closely related alerts, or simply
                  alerts with the same interval, into individual groups.  You are also free
                  to create AlertingRule resources with only a single rule group, but be
                  aware that this can have a performance impact on Prometheus if the group is
                  extremely large or has very complex query expressions to evaluate.
                  Spreading very complex rules across multiple groups to allow them to be
                  processed in parallel is also a common use-case.
                items:
                  description: RuleGroup is a list of sequentially evaluated alerting
                    rules.
                  properties:
                    interval:
                      description: |-
                        interval is how often rules in the group are evaluated.  If not specified,
                        it defaults to the global.evaluation_interval configured in Prometheus,
                        which itself defaults to 30 seconds.  You can check if this value has been
                        modified from the default on your cluster by inspecting the platform
                        Prometheus configuration:
                        The relevant field in that resource is: spec.evaluationInterval
                      maxLength: 2048
                      pattern: ^(0|(([0-9]+)y)?(([0-9]+)w)?(([0-9]+)d)?(([0-9]+)h)?(([0-9]+)m)?(([0-9]+)s)?(([0-9]+)ms)?)$
                      type: string
                    name:
                      description: name is the name of the group.
                      maxLength: 2048
                      minLength: 1
                      type: string
                    rules:
                      description: |-
                        rules is a list of sequentially evaluated alerting rules.  Prometheus may
                        process rule groups in parallel, but rules within a single group are always
                        processed sequentially, and all rules are processed.
                      items:
                        description: |-
                          Rule describes an alerting rule.
                          See Prometheus documentation:
                          - https://www.prometheus.io/docs/prometheus/latest/configuration/alerting_rules
                        properties:
                          alert:
                            description: |-
                              alert is the name of the alert. Must be a valid label value, i.e. may
                              contain any Unicode character.
                            maxLength: 2048
                            minLength: 1
                            type: string
                          annotations:
                            additionalProperties:
                              type: string
                            description: |-
                              annotations to add to each alert.  These are values that can be used to
                              store longer additional information that you won't query on, such as alert
                              descriptions or runbook links.
                            type: object
                          expr:
                            anyOf:
                            - type: integer
                            - type: string
                            description: |-
                              expr is the PromQL expression to evaluate. Every evaluation cycle this is
                              evaluated at the current time, and all resultant time series become pending
                              or firing alerts.  This is most often a string representing a PromQL
                              expression, e.g.: mapi_current_pending_csr > mapi_max_pending_csr
                              In rare cases this could be a simple integer, e.g. a simple "1" if the
                              intent is to create an alert that is always firing.  This is sometimes used
                              to create an always-firing "Watchdog" alert in order to ensure the alerting
                              pipeline is functional.
                            x-kubernetes-int-or-string: true
                          for:
                            description: |-
                              for is the time period after which alerts are considered firing after first
                              returning results.  Alerts which have not yet fired for long enough are
                              considered pending.
                            maxLength: 2048
                            pattern: ^(0|(([0-9]+)y)?(([0-9]+)w)?(([0-9]+)d)?(([0-9]+)h)?(([0-9]+)m)?(([0-9]+)s)?(([0-9]+)ms)?)$
                            type: string
                          labels:
                            additionalProperties:
                              type: string
                            description: |-
                              labels to add or overwrite for each alert.  The results of the PromQL
                              expression for the alert will result in an existing set of labels for the
                              alert, after evaluating the expression, for any label specified here with
                              the same name as a label in that set, the label here wins and overwrites
                              the previous value.  These should typically be short identifying values
                              that may be useful to query against.  A common example is the alert
                              severity, where one sets `severity: warning` under the `labels` key:
                            type: object
                        required:
                        - alert
                        - expr
                        type: object
                      minItems: 1
                      type: array
                  required:
                  - name
                  - rules
                  type: object
                minItems: 1
                type: array
                x-kubernetes-list-map-keys:
                - name
                x-kubernetes-list-type: map
            required:
            - groups
            type: object
          status:
            description: status describes the current state of this AlertOverrides
              object.
            properties:
              observedGeneration:
                description: observedGeneration is the last generation change you've
                  dealt with.
                format: int64
                type: integer
              prometheusRule:
                description: |-
                  prometheusRule is the generated PrometheusRule for this AlertingRule.  Each
                  AlertingRule instance results in a generated PrometheusRule object in the
                  same namespace, which is always the openshift-monitoring namespace.
                properties:
                  name:
                    description: name of the referenced PrometheusRule.
                    maxLength: 2048
                    minLength: 1
                    type: string
                required:
                - name
                type: object
            type: object
        required:
        - spec
        type: object
    served: true
    storage: true
    subresources:
      status: {}
status:
  acceptedNames:
    kind: AlertingRule
    listKind: AlertingRuleList
    plural: alertingrules
    singular: alertingrule
  conditions:
  - lastTransitionTime: "2025-10-27T11:18:18Z"
    message: no conflicts found
    reason: NoConflicts
    status: "True"
    type: NamesAccepted
  - lastTransitionTime: "2025-10-27T11:18:18Z"
    message: the initial names have been accepted
    reason: InitialNamesAccepted
    status: "True"
    type: Established
  storedVersions:
  - v1
