Alerts amp Providers

Overview

The Flux Notification Controller bridges external event sources (e.g., GitHub, S3 buckets, Helm repositories, Docker registries) with notification targets (Slack, Teams, Discord, Telegram). It comprises:

• Receiver: Watches changes in external sources and informs Flux controllers.
• Provider: Encodes and delivers events to external systems based on defined channels and formats.

Events emitted by Flux controllers (Source, Kustomize, Helm, Image) are matched against Alert rules and dispatched via Providers.

Configuring Slack Notifications

In this example, we’ll use Slack’s legacy incoming webhook API to post Flux events to a channel.

1. Create the Slack Webhook Secret

Store your webhook URL in the flux-system namespace:

kubectl -n flux-system create secret generic slack-webhook \
  --from-literal=address=https://hooks.slack.com/services/SLACK/WEBHOOK/URL

2. Define an AlertProvider

Create an AlertProvider named slack-example of type slack, pointing at the general channel and referencing the slack-webhook secret:

flux create alert-provider slack-example \
  --type slack \
  --channel general \
  --username flux-webhook \
  --secret-ref slack-webhook

3. Create an Alert

Define an Alert resource to filter and route events of info severity from all Flux controllers in flux-system:

flux create alert slack-notification \
  --event-severity info \
  --provider-ref slack-example \
  --event-source GitRepository/* \
  --event-source HelmRepository/* \
  --event-source Kustomization/* \
  --event-source Bucket/* \
  --event-source OCIRepository/* \
  --event-source HelmChart/* \
  --event-source HelmRelease/* \
  --event-source ImageRepository/* \
  --event-source ImagePolicy/* \
  --event-source ImageUpdateAutomation/*

Flux Notification Resources at a Glance

References

• Flux Notification Controller
• Kubernetes Secrets
• Slack Incoming Webhooks