Get phone and SMS alerts fromFlux
Flux keeps your Kubernetes clusters in sync with Git. When a Kustomization fails validation or a HelmRelease can't install, Spike pages whoever is on call by phone, SMS, Slack or email, and escalates until someone answers.
Set up with AI
I use Flux for monitoring and Spike for on-call and incident management. Walk me through connecting them: create a Flux integration in Spike, copy its webhook URL, and add that webhook to Flux alert settings. Then help me send a test alert to confirm incidents show up in Spike.
What is Flux?
Flux is a GitOps toolkit for Kubernetes, and a CNCF graduated project. It watches a Git repository, Helm repository or bucket, and continuously reconciles the cluster toward what is declared there. Its controllers each report on the objects they manage — Kustomizations, HelmReleases, GitRepositories and more — and record why a reconciliation succeeded or failed.
Pointed at Spike through a generic notification-controller Provider, those events become pages. A failed validation, a failed health check or an unreachable repository opens an incident whose title is Flux’s own sentence about what happened, so the on-call engineer knows what broke before opening the cluster. Who gets paged, and how hard, is decided in Spike with alert routing rules, and an incident nobody acknowledges climbs the escalation policy.
Every Flux object carries a Kubernetes UID, and Spike uses it to keep alerts together. A repeat failure for the same object joins the open incident rather than paging again, while two different objects stay two incidents. When Flux reports a successful reconciliation for that object, Spike resolves the incident automatically. Progress and dependency notices are accepted but never open an incident.
How to set up Flux alerts
Every Spike integration is a unique webhook URL. Paste it into Flux and alerts start flowing — no agents, no code.
Step 1: Create a Flux integration in Spike
In your Spike dashboard, open Integrations and choose Flux. Spike generates a unique webhook URL for this integration — copy it, and attach the integration to the service and escalation policy that should answer these alerts.
Step 2: Add a generic Provider in Flux
Create a notification-controller Provider of type generic that points at the Spike webhook URL, keeping the URL in a Kubernetes Secret rather than in Git.
Step 3: Create an Alert for the objects you care about
Create an Alert that references the Provider and lists the event sources to watch, such as Kustomizations, HelmReleases and GitRepositories. Keep eventSeverity at info (the default), which includes errors, so Spike hears both failures and the success that follows.
Step 4: Watch a failure become an incident
When a reconciliation fails, Spike opens an incident titled with Flux's own message. Repeat failures for the same object join that incident, and when Flux reconciles successfully the incident resolves itself.
That's it — Flux alerts now page whoever is on call.
