State, not events
Reactor polls the UniFi Network API and reconciles against what it observes. A dropped webhook, a network blip or a controller restart cannot strand your cluster in the wrong mode, because the next observation corrects it.
UniFi Reactor
Your WAN fails over to the 5G backup at 3am. Nothing in the cluster notices. UniFi Reactor is the operator that makes it notice.
Reversal is explicit
An Automation says what to do when a condition starts holding, and separately what it wants once it stops. Nothing is inferred, undoing is never guessed, and every execution is recorded in the resource’s status.
One workload, many Automations
A target’s level is arbitrated across every Automation pointing at it. Two can pause the same workload for unrelated reasons, and it stays paused until neither wants it down.
Safe by default
A dedicated ServiceAccount with exactly the verbs it needs, no cluster-admin,
no arbitrary shell execution, and credentials read from Kubernetes Secrets.
The actions that leave the cluster are refused until you say where they may go.
Start here
Section titled “Start here”What Reactor is
The problem it solves, and the five properties that decide how it behaves.
Install
A Helm install, an API key, and a log line that proves it can see your hardware.
Your first Automation
Pause downloads while the WAN is on the backup uplink, and resume them when it recovers — one resource covers both directions.
State keys
Everything Reactor can match on: WAN and internet, power and UPS, the device fleet, and switchable UPS outlets.