Skip to main content
The Kubernetes integration watches events in your clusters — pod crashes, deployment updates, service changes, and more — and records them as pulses in Rootly. Pulses give responders infrastructure context directly on the incident timeline, so you can quickly answer the question “what changed?” when investigating an incident. Kubernetes integration can watch different resources and create pulses:
Kubernetes integration

Kubernetes integration

​
How it works

Cluster events are captured by kubewatch, an open-source Kubernetes watcher that you deploy in your cluster, and forwarded to a unique webhook URL that Rootly generates for your workspace. You choose which resource types kubewatch monitors — deployments, pods, services, nodes, jobs, namespaces, and other resource types are supported. Each event appears as a pulse with a summary in the form [k8s][{resource kind}] {event text}, along with labels and refs identifying the resource and namespace.

​
Linking pulses to services

Rootly automatically associates Kubernetes pulses with your services by matching the Kubernetes Deployment Name field on the service against the event’s resource name. The match is partial, so a service named api-server will match events from any deployment containing api-server in its name. Set this field on each service you want correlated with cluster events.
If pulse volume gets noisy, narrow the resource types enabled in your kubewatch configuration — disabling low-signal resources like secrets and ConfigMaps significantly reduces noise.
Ready to configure the Kubernetes integration? See Kubernetes integration setup.