Grafana Alloy is the new name for our distribution of the OTel collector. Grafana Agent has been deprecated and is in Long-Term Support (LTS) through October 31, 2025. Grafana Agent will reach an End-of-Life (EOL) on November 1, 2025. Read more about why we recommend migrating to Grafana Alloy.

Important: This documentation is about an older version. It's relevant only to the release noted, many of the features and functions have been updated or replaced. Please view the current version.



BETA: This is a beta component. Beta components are subject to breaking changes, and may be replaced with equivalent functionality that cover the same use case.

mimir.rules.kubernetes discovers PrometheusRule Kubernetes resources and loads them into a Mimir instance.

  • Multiple mimir.rules.kubernetes components can be specified by giving them different labels.
  • Kubernetes label selectors can be used to limit the Namespace and PrometheusRule resources considered during reconciliation.
  • Compatible with the Ruler APIs of Grafana Mimir, Grafana Cloud, and Grafana Enterprise Metrics.
  • Compatible with the PrometheusRule CRD from the prometheus-operator.
  • This component accesses the Kubernetes REST API from within a Pod.

NOTE: This component requires Role-based access control (RBAC) to be setup in Kubernetes in order for the Agent to access it via the Kubernetes REST API. For an example RBAC configuration please click here.


mimir.rules.kubernetes "LABEL" {
  address = MIMIR_RULER_URL


mimir.rules.kubernetes supports the following arguments:

addressstringURL of the Mimir ruler.yes
tenant_idstringMimir tenant
use_legacy_routesboolWhether to use deprecated ruler API endpoints.falseno
sync_intervaldurationAmount of time between reconciliations with Mimir.“30s”no
mimir_namespace_prefixstringPrefix used to differentiate multiple agent deployments.“agent”no
bearer_tokensecretBearer token to authenticate
bearer_token_filestringFile containing a bearer token to authenticate
proxy_urlstringHTTP proxy to proxy requests
follow_redirectsboolWhether redirects returned by the server should be followed.trueno
enable_http2boolWhether HTTP2 is supported for requests.trueno

At most one of the following can be provided:

If no tenant_id is provided, the component assumes that the Mimir instance at address is running in single-tenant mode and no X-Scope-OrgID header is sent.

The sync_interval argument determines how often Mimir’s ruler API is accessed to reload the current state of rules. Interaction with the Kubernetes API works differently. Updates are processed as events from the Kubernetes API server according to the informer pattern.

The mimir_namespace_prefix argument can be used to separate the rules managed by multiple agent deployments across your infrastructure. It should be set to a unique value for each deployment.


The following blocks are supported inside the definition of mimir.rules.kubernetes:

rule_namespace_selectorlabel_selectorLabel selector for Namespace
rule_namespace_selector > match_expressionmatch_expressionLabel match expression for Namespace
rule_selectorlabel_selectorLabel selector for PrometheusRule
rule_selector > match_expressionmatch_expressionLabel match expression for PrometheusRule
basic_authbasic_authConfigure basic_auth for authenticating to the
authorizationauthorizationConfigure generic authorization to the
oauth2oauth2Configure OAuth2 for authenticating to the
oauth2 > tls_configtls_configConfigure TLS settings for connecting to the
tls_configtls_configConfigure TLS settings for connecting to the

The > symbol indicates deeper levels of nesting. For example, oauth2 > tls_config refers to a tls_config block defined inside an oauth2 block.

label_selector block

The label_selector block describes a Kubernetes label selector for rule or namespace discovery.

The following arguments are supported:

match_labelsmap(string)Label keys and values used to discover resources.{}yes

When the match_labels argument is empty, all resources will be matched.

match_expression block

The match_expression block describes a Kubernetes label match expression for rule or namespace discovery.

The following arguments are supported:

keystringThe label name to match against.yes
operatorstringThe operator to use when matching.yes
valueslist(string)The values used when

The operator argument should be one of the following strings:

  • "In"
  • "NotIn"
  • "Exists"
  • "DoesNotExist"

The values argument must not be provided when operator is set to "Exists" or "DoesNotExist".

basic_auth block

password_filestringFile containing the basic auth
passwordsecretBasic auth
usernamestringBasic auth

password and password_file are mutually exclusive, and only one can be provided inside a basic_auth block.

authorization block

credentials_filestringFile containing the secret
typestringAuthorization type, for example, “Bearer”.no

credential and credentials_file are mutually exclusive, and only one can be provided inside an authorization block.

oauth2 block

client_idstringOAuth2 client
client_secret_filestringFile containing the OAuth2 client
client_secretsecretOAuth2 client
endpoint_paramsmap(string)Optional parameters to append to the token
proxy_urlstringOptional proxy URL for OAuth2
scopeslist(string)List of scopes to authenticate
token_urlstringURL to fetch the token

client_secret and client_secret_file are mutually exclusive, and only one can be provided inside an oauth2 block.

The oauth2 block may also contain a separate tls_config sub-block.

tls_config block

ca_pemstringCA PEM-encoded text to validate the server
ca_filestringCA certificate to validate the server
cert_pemstringCertificate PEM-encoded text for client
cert_filestringCertificate file for client
insecure_skip_verifyboolDisables validation of the server
key_filestringKey file for client
key_pemsecretKey PEM-encoded text for client
min_versionstringMinimum acceptable TLS
server_namestringServerName extension to indicate the name of the

The following pairs of arguments are mutually exclusive and can’t both be set simultaneously:

  • ca_pem and ca_file
  • cert_pem and cert_file
  • key_pem and key_file

When configuring client authentication, both the client certificate (using cert_pem or cert_file) and the client key (using key_pem or key_file) must be provided.

When min_version is not provided, the minimum acceptable TLS version is inherited from Go’s default minimum version, TLS 1.2. If min_version is provided, it must be set to one of the following strings:

  • "TLS10" (TLS 1.0)
  • "TLS11" (TLS 1.1)
  • "TLS12" (TLS 1.2)
  • "TLS13" (TLS 1.3)

Exported fields

mimir.rules.kubernetes does not export any fields.

Component health

mimir.rules.kubernetes is reported as unhealthy if given an invalid configuration or an error occurs during reconciliation.

Debug information

mimir.rules.kubernetes exposes resource-level debug information.

The following are exposed per discovered PrometheusRule resource:

  • The Kubernetes namespace.
  • The resource name.
  • The resource uid.
  • The number of rule groups.

The following are exposed per discovered Mimir rule namespace resource:

  • The namespace name.
  • The number of rule groups.

Only resources managed by the component are exposed - regardless of how many actually exist.

Debug metrics

Metric NameTypeDescription
mimir_rules_config_updates_totalcounterNumber of times the configuration has been updated.
mimir_rules_events_totalcounterNumber of events processed, partitioned by event type.
mimir_rules_events_failed_totalcounterNumber of events that failed to be processed, partitioned by event type.
mimir_rules_events_retried_totalcounterNumber of events that were retried, partitioned by event type.
mimir_rules_client_request_duration_secondshistogramDuration of requests to the Mimir API.


This example creates a mimir.rules.kubernetes component that loads discovered rules to a local Mimir instance under the team-a tenant. Only namespaces and rules with the agent label set to yes are included.

mimir.rules.kubernetes "local" {
    address = "mimir:8080"
    tenant_id = "team-a"

    rule_namespace_selector {
        match_labels = {
            agent = "yes",

    rule_selector {
        match_labels = {
            agent = "yes",

This example creates a mimir.rules.kubernetes component that loads discovered rules to Grafana Cloud.

mimir.rules.kubernetes "default" {
    basic_auth {
        username = "GRAFANA_CLOUD_USER"
        password = "GRAFANA_CLOUD_API_KEY"
        // Alternatively, load the password from a file:
        // password_file = "GRAFANA_CLOUD_API_KEY_PATH"

The following example is an RBAC configuration for Kubernetes. It authorizes the Agent to query the Kubernetes REST API:

apiVersion: v1
kind: ServiceAccount
  name: grafana-agent
  namespace: default
kind: ClusterRole
  name: grafana-agent
- apiGroups: [""]
  resources: ["namespaces"]
  verbs: ["get", "list", "watch"]
- apiGroups: [""]
  resources: ["prometheusrules"]
  verbs: ["get", "list", "watch"]
kind: ClusterRoleBinding
  name: grafana-agent
- kind: ServiceAccount
  name: grafana-agent
  namespace: default
  kind: ClusterRole
  name: grafana-agent