Notification Controller
What you'll learn: How to configure alerts and notifications for Flux events using Provider and Alert resources to stay informed about your GitOps deployments.
The Core Idea
The Notification Controller is Flux's messaging hub that watches for events across all other Flux controllers and sends alerts to external systems. Think of it as a newsroom reporter: it observes what's happening in your cluster (reconciliation failures, successful syncs, policy violations) and broadcasts those stories to channels you care about—Slack, Microsoft Teams, webhooks, or any other notification platform.
How It Works
You define two types of resources:
Provider - Specifies where notifications go (Slack, Discord, generic webhook, etc.) and includes connection details like URLs and authentication tokens.
Alert - Specifies what to watch and which Provider to use. You can filter by severity (info, error), event type, and specific sources like a GitRepository or HelmRelease.
When a Flux controller emits an event matching your Alert criteria, the Notification Controller forwards that event to the configured Provider.
Example Concepts
A Provider might point to a Slack webhook URL for your DevOps channel. An Alert watches your production HelmRelease resources and fires only on errors or warnings. When a Helm deployment fails, you get an immediate Slack message with details about what went wrong.
This creates a real-time feedback loop: your Git commits trigger Flux reconciliation, and any issues are immediately surfaced where your team already communicates, rather than requiring manual cluster inspection.
Key Takeaway: The Notification Controller connects Flux events to your external alerting infrastructure using Provider (destination) and Alert (filter/trigger) resources, enabling proactive monitoring of your GitOps workflows.