1.7 KiB
1.7 KiB
| title | description | published | date | tags | editor | dateCreated |
|---|---|---|---|---|---|---|
| Audit - kuma.yaml | Gremlin audit report 2026-04-13 | true | 2026-04-13T11:20:00.830Z | gremlin,audit | markdown | 2026-04-13T11:20:00.830Z |
Audit Report — kuma.yaml
Date: 2026-04-13
File: swarm/kuma.yaml
Type: Docker Swarm
Verdict: FAIL
SWARM AUDIT
-
Homepage labels:
homepage.group,homepage.name,homepage.icon,homepage.href, andhomepage.descriptionare all present and correctly formatted.- PASS
-
Uptime Kuma labels:
kuma.kuma.http.nameandkuma.kuma.http.urlare both present and correctly formatted.- PASS
-
Caddy labels on exposed services:
- The Caddy label
caddy=kuma.netgrimoire.comis present for thekumaservice, but it seems redundant since it's also a homepage label. - The Caddy label
caddy.reverse_proxy=kuma:3001is not present for any service. It should be added to ensure that Caddy correctly proxies requests to Kuma. - FAIL: Missing
caddy.reverse_proxy=kuma:3001
- The Caddy label
-
Placement constraints:
- The constraint
- node.hostname == docker3is present for thekumaservice, ensuring it runs on the specified node. - PASS
- The constraint
-
Volumes use /DockerVol/ path convention:
- Both
kumaandautokumavolumes follow the/DockerVol/<service>path convention. - PASS
- Both
-
Network references external netgrimoire overlay:
- The
netgrimoirenetwork is correctly referenced as an external network. - PASS
- The
VERDICT: FAIL
The audit identified one issue that needs to be addressed:
- The Caddy label
caddy.reverse_proxy=kuma:3001is missing for thekumaservice, which prevents Caddy from properly proxying requests to Kuma.