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.
loki.source.kubernetes
EXPERIMENTAL: This is an experimental component. Experimental components are subject to frequent breaking changes, and may be removed with no equivalent replacement.
loki.source.kubernetes tails logs from Kubernetes containers using the
Kubernetes API. It has the following benefits over loki.source.file:
- It works without a privileged container.
- It works without a root user.
- It works without needing access to the filesystem of the Kubernetes node.
- It doesn’t require a DaemonSet to collect logs, so one agent could collect logs for the whole cluster.
NOTE: Because
loki.source.kubernetesuses the Kubernetes API to tail logs, it uses more network traffic and CPU consumption of Kubelets thanloki.source.file.
Multiple loki.source.kubernetes components can be specified by giving them
different labels.
Usage
loki.source.kubernetes "LABEL" {
targets = TARGET_LIST
forward_to = RECEIVER_LIST
}Arguments
The component starts a new reader for each of the given targets and fans out
log entries to the list of receivers passed in forward_to.
loki.source.kubernetes supports the following arguments:
Each target in targets must have the following labels:
__meta_kubernetes_namespaceor__pod_namespace__to specify the namespace of the pod to tail.__meta_kubernetes_pod_nameor__pod_name__to specify the name of the pod to tail.__meta_kubernetes_pod_container_nameor__pod_container_name__to specify the container within the pod to tail.__meta_kubernetes_pod_uidor__pod_uid__to specify the UID of the pod to tail.
By default, all of these labels are present when the output
discovery.kubernetes is used.
A log tailer is started for each unique target in targets. Log tailers will
reconnect with exponential backoff to Kubernetes if the log stream returns
before the container has permanently terminated.
Blocks
The following blocks are supported inside the definition of
loki.source.kubernetes:
The > symbol indicates deeper levels of nesting. For example, client > basic_auth refers to a basic_auth block defined
inside a client block.
client block
The client block configures the Kubernetes client used to tail logs from
containers. If the client block isn’t provided, the default in-cluster
configuration with the service account of the running Grafana Agent pod is
used.
The following arguments are supported:
At most one of the following can be provided:
basic_auth block
password and password_file are mutually exclusive and only one can be
provided inside of a basic_auth block.
authorization block
credential and credentials_file are mutually exclusive and only one can be
provided inside of an authorization block.
oauth2 block
client_secret and client_secret_file are mutually 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
The following pairs of arguments are mutually exclusive and cannot both be set simultaneously:
ca_pemandca_filecert_pemandcert_filekey_pemandkey_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
loki.source.kubernetes does not export any fields.
Component health
loki.source.kubernetes is only reported as unhealthy if given an invalid
configuration.
Debug information
loki.source.kubernetes exposes some target-level debug information per
target:
- The labels associated with the target.
- The full set of labels which were found during service discovery.
- The most recent time a log line was read and forwarded to the next components in the pipeline.
- The most recent error from tailing, if any.
Debug metrics
loki.source.kubernetes does not expose any component-specific debug metrics.
Example
This example collects logs from all Kubernetes pods and forwards them to a
loki.write component so they are written to Loki.
discovery.kubernetes "pods" {
role = "pod"
}
loki.source.kubernetes "pods" {
targets = discovery.kubernetes.pods.targets
forward_to = [loki.write.local.receiver]
}
loki.write "local" {
endpoint {
url = env("LOKI_URL")
}
}


