What's new from Grafana Labsbreadcrumb arrow Added provenance support to alerting notification app platform APIs
What's new from Grafana Labs
What's new from Grafana Labs
Grafana Cloud Generally Available Open source Enterprise Generally Available Alerting
Release date: 2026-04-07

Added provenance support to alerting notification app platform APIs

The grafana.com/provenance annotation on alerting notification resources is now correctly read and enforced when writing using the Kubernetes-style API. Previously, provenance was hardcoded to none on all Kubernetes API writes, so the annotation was silently ignored. It is now respected. Setting it requires one of the following permissions:

  • alert.provisioning:write
  • alert.notifications.provisioning:write
  • alert.provisioning.provenance:write

Callers without one of these permissions can still create, update spec fields, and delete notification resources — they just cannot escalate a resource’s provenance status. This brings the Kubernetes API into parity with the HTTP provisioning API, which already enforced this check. File provisioning is unaffected and continues to use relaxed provenance semantics.

Affected resources (receivers, notification policies, templates, mute timings, inhibition rules):

ResourcePath
Receivers/apis/notifications.alerting.grafana.app/v1beta1/namespaces/{namespace}/receivers
Notification policies/apis/notifications.alerting.grafana.app/v1beta1/namespaces/{namespace}/routingtrees
Templates/apis/notifications.alerting.grafana.app/v1beta1/namespaces/{namespace}/templategroups
Mute timings/apis/notifications.alerting.grafana.app/v1beta1/namespaces/{namespace}/timeintervals
Inhibition rules/apis/notifications.alerting.grafana.app/v1beta1/namespaces/{namespace}/inhibitionrules

Action required

If you manage notification resources with the Kubernetes API and set the grafana.com/provenance annotation, verify the calling identity has one of the required permissions. Callers that never set this annotation are unaffected.

Related What's new posts
docs icon 2026-04-07
Legacy Alertmanager configuration API endpoints changed
docs icon 2026-03-31
Alertmanager status endpoint requires a new permission
docs icon 2026-03-25
Attribution Alerts