Kubyl Mobile can notify you about firing Alertmanager alerts, failed Argo CD syncs and nodes that go NotReady.
How it works
The phone registers its push token with your server. The server decides what is worth a notification and sends it through a relay at https://kubyl.dev/api/push. The relay holds the Apple and Google credentials and forwards the message; it keeps no tokens and no payloads.
- Each notification is encrypted for one device, with a key the phone made and keeps in its Keychain or Keystore. Apple, Google and the relay see only a generic text (“2 alerts firing”) and opaque ids. Cluster names, alert text and object names are inside the encrypted part.
- The relay checks your install's signature and that its license is active, so push stops when the server is Unlicensed or Locked.
- The server watches every connected cluster that some device wants to hear about. It connects to them for that, even when no phone is open.
Choose what you get
Turn notifications on in More, Notifications (the server row appears when your server supports push). The system permission prompt appears only when you flip that switch, never at install. There you set, per device and per cluster: alerts firing or resolved, sync failed, node not ready, a minimum severity and which clusters. A Test button sends a test notification through your server and the relay and reports the outcome (sent, rate limited, not registered or failed).
Tapping a notification opens the alert, the Argo CD application or the node it is about. The phone registers an Apple (APNs) or Google (FCM) token plus a key made on the device for this server, so pairing another server needs its own switch. Pushes need a Licensed or Grace server (license_required otherwise), and a revoked device loses its registration.
Limits
The server sends at most 10 pushes per device per 10 minutes (the rest fold into one message) and never repeats the same event within 15 minutes.