fluxcd-notification-controller

FluxCD Notification Controller is an event forwarder and notification dispatcher for the FluxCD GitOps Toolkit controllers.

  • Communication
  • Development
  • Tools & Utilities
FluxCD Notification Controller is an event forwarder and notification dispatcher for the FluxCD GitOps Toolkit controllers. It watches events from Git providers, Kubernetes Alertmanager, and other Toolkit controllers, then delivers notifications to channels such as Slack, Microsoft Teams, email, and webhooks, keeping your team informed of changes and incidents in your GitOps environment.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

72/100 Good

Maintained
100last commit 3 days ago
Popular
45182 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
10064 MB minimum RAM
Security check
74no serious findings, 5 minor, CI, tests, OpenSSF Scorecard 8.1/10
GitHub stars
182
Open issues
80
Last commit
2026-11-18
Latest release
v1.10.0
License
Apache-2.0
Activity
declining

Checked 2 days ago - source: GitHub (fluxcd/notification-controller)

Resources & Compatibility

Minimum requirements: 64 MB RAM.

Checked 23 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Point Flux CD at the chart Create a HelmRepository, HelmChart, or OCIRepository object first, then set the HelmRelease chartRef to that name. If the name is missing or wrong, Flux CD cannot find the chart and the app will not install. source
  • Set install timeout and retries Under install, give Helm enough time to finish and set remediation retries to 1-3. If an install fails because something was temporarily busy, retries can let it try again. source
  • Run chart tests if they exist Enable HelmRelease tests only after you know the chart has working test hooks. It can catch install problems early, but bad tests can make the release look failed. source

Fetched 42 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Which Flux API does notification-controller implement?

It implements the notification.toolkit.fluxcd.io API based on the Flux RFC specifications.

Which external systems can send events to the Notification Controller?

It handles events from external systems such as GitHub, GitLab, Bitbucket, Harbor, and Jenkins.

Where should I report issues with alerts or webhook receivers?

File them against the notification-controller repository, which covers handling inbound and outbound events, alerts, and webhook receivers.

Answers sourced from fluxcd.io, fluxcd.io, github.com

Community

Collected 48 days ago - public community threads