Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions kubernetes/apps/uptime-kuma/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,8 @@

Uptime Kuma runs outbound HTTP and TCP checks against endpoints the operator cares about and posts state changes to a Discord webhook. It is an operator convenience, not a service anyone else depends on: its own availability is bounded by devata's, and devata is a homelab behind a residential uplink. Anything that must alert when the homelab itself is down needs an external watcher, which this component deliberately does not try to be.

The Application carries the platform tier: Kuma is operator tooling beside Grafana and Alertmanager, not a showcase workload, and the public homelab page lists platform-tier apps in its stack row.

The component exists alongside kube-prometheus-stack on purpose. Prometheus and Alertmanager watch the cluster from inside. Kuma watches the world from the cluster's point of view, with a status page and a notification path that takes a minute to configure rather than a ruleset. The two do not share alert routes.

## Safety model
Expand Down
2 changes: 1 addition & 1 deletion kubernetes/clusters/devata/uptime-kuma.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ metadata:
name: uptime-kuma
namespace: argocd
labels:
devata.pragalva.me/tier: workload
devata.pragalva.me/tier: platform
spec:
project: default
sources:
Expand Down
Loading