Caution
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.
mimir.rules.kubernetes
mimir.rules.kubernetes discovers PrometheusRule Kubernetes resources and
loads them into a Mimir instance.
- Multiple
mimir.rules.kubernetescomponents can be specified by giving them different labels. - Kubernetes label selectors can be used to limit the
NamespaceandPrometheusRuleresources considered during reconciliation. - Compatible with the Ruler APIs of Grafana Mimir, Grafana Cloud, and Grafana Enterprise Metrics.
- Compatible with the
PrometheusRuleCRD from the prometheus-operator.
Usage
mimir.rules.kubernetes "LABEL" {
address = MIMIR_RULER_URL
}Arguments
mimir.rules.kubernetes supports the following arguments:
| Name | Type | Description | Default | Required |
|---|---|---|---|---|
address | string | URL of the Mimir ruler. | yes | |
tenant_id | string | Mimir tenant ID. | no | |
use_legacy_routes | bool | Whether to use deprecated ruler API endpoints. | false | no |
sync_interval | duration | Amount of time between reconciliations with Mimir. | “30s” | no |
mimir_namespace_prefix | string | Prefix used to differentiate multiple agent deployments. | “agent” | no |
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.
Blocks
The following blocks are supported inside the definition of
mimir.rules.kubernetes:
| Hierarchy | Block | Description | Required |
|---|---|---|---|
| rule_namespace_selector | label_selector | Label selector for Namespace resources. | no |
| rule_namespace_selector > match_expression | match_expression | Label match expression for Namespace resources. | no |
| rule_selector | label_selector | Label selector for PrometheusRule resources. | no |
| rule_selector > match_expression | match_expression | Label match expression for PrometheusRule resources. | no |
| http_client_config | http_client_config | HTTP client settings when connecting to the endpoint. | no |
| http_client_config > basic_auth | basic_auth | Configure basic_auth for authenticating to the endpoint. | no |
| http_client_config > authorization | authorization | Configure generic authorization to the endpoint. | no |
| http_client_config > oauth2 | oauth2 | Configure OAuth2 for authenticating to the endpoint. | no |
| http_client_config > oauth2 > tls_config | tls_config | Configure TLS settings for connecting to the endpoint. | no |
| http_client_config > tls_config | tls_config | Configure TLS settings for connecting to the endpoint. | no |
The > symbol indicates deeper levels of nesting. For example,
http_client_config > basic_auth refers to a basic_auth block defined inside
an http_client_config block.
label_selector block
The label_selector block describes a Kubernetes label selector for rule or namespace discovery.
The following arguments are supported:
| Name | Type | Description | Default | Required |
|---|---|---|---|---|
match_labels | map(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:
| Name | Type | Description | Default | Required |
|---|---|---|---|---|
key | string | The label name to match against. | yes | |
operator | string | The operator to use when matching. | yes | |
values | []string | The values used when matching. | no |
The operator argument should be one of the following strings:
"in""notin""exists"
http_client_config block
The http_client_config configures settings used to connect to the Mimir API.
| Name | Type | Description | Default | Required |
|---|---|---|---|---|
bearer_token | secret | Bearer token to authenticate with. | no | |
bearer_token_file | string | File containing a bearer token to authenticate with. | no | |
proxy_url | string | HTTP proxy to proxy requests through. | no | |
follow_redirects | bool | Whether redirects returned by the server should be followed. | true | no |
enable_http_2 | bool | Whether HTTP2 is supported for requests. | true | no |
bearer_token, bearer_token_file, basic_auth, authorization, and
oauth2 are mutually exclusive and only one can be provided inside of a
http_client_config block.
basic_auth block
| Name | Type | Description | Default | Required |
|---|---|---|---|---|
username | string | Basic auth username. | no | |
password | secret | Basic auth password. | no | |
password_file | string | File containing the basic auth password. | no |
password and password_file are mututally exclusive and only one can be
provided inside of a basic_auth block.
authorization block
| Name | Type | Description | Default | Required |
|---|---|---|---|---|
type | string | Authorization type, for example, “Bearer”. | no | |
credential | secret | Secret value. | no | |
credentials_file | string | File containing the secret value. | no |
credential and credentials_file are mutually exclusive and only one can be
provided inside of an authorization block.
oauth2 block
| Name | Type | Description | Default | Required |
|---|---|---|---|---|
client_id | string | OAuth2 client ID. | no | |
client_secret | secret | OAuth2 client secret. | no | |
client_secret_file | string | File containing the OAuth2 client secret. | no | |
scopes | list(string) | List of scopes to authenticate with. | no | |
token_url | string | URL to fetch the token from. | no | |
endpoint_params | map(string) | Optional parameters to append to the token URL. | no | |
proxy_url | string | Optional proxy URL for OAuth2 requests. | no |
client_secret and client_secret_file are mututally exclusive and only one
can be provided inside of an oauth2 block.
The oauth2 block may also contain its own separate tls_config sub-block.
tls_config block
| Name | Type | Description | Default | Required |
|---|---|---|---|---|
ca_file | string | CA certificate to validate the server with. | no | |
cert_file | string | Certificate file for client authentication. | no | |
key_file | string | Key file for client authentication. | no | |
server_name | string | ServerName extension to indicate the name of the server. | no | |
insecure_skip_verify | bool | Disables validation of the server certificate. | no | |
min_version | string | Minimum acceptable TLS version. | no |
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 Name | Type | Description |
|---|---|---|
mimir_rules_config_updates_total | counter | Number of times the configuration has been updated. |
mimir_rules_events_total | counter | Number of events processed, partitioned by event type. |
mimir_rules_events_failed_total | counter | Number of events that failed to be processed, partitioned by event type. |
mimir_rules_events_retried_total | counter | Number of events that were retried, partitioned by event type. |
mimir_rules_client_request_duration_seconds | histogram | Duration of requests to the Mimir API. |
Example
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" {
address = "GRAFANA_CLOUD_METRICS_URL"
http_client_config {
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"
}
}
}


