1.6 KiB
1.6 KiB
| title | description | published | date | tags | editor | dateCreated |
|---|---|---|---|---|---|---|
| Audit - kopia.yaml | Gremlin audit report 2026-04-27 | true | 2026-04-27T11:19:18.771Z | gremlin,audit | markdown | 2026-04-27T11:19:18.771Z |
Audit Report — kopia.yaml
Date: 2026-04-27
File: swarm/kopia.yaml
Type: Docker Swarm
Verdict: FAIL
SWARM AUDIT RESULTS
-
Homepage labels:
- PASS: homepage.group, homepage.name, homepage.icon, homepage.href, homepage.description are all correctly configured.
-
Uptime Kuma labels:
- PASS: kuma.kopia.http.name and kuma.kopia.http.url are correctly set.
-
Caddy labels on exposed services:
- PASS: caddy=kopia.netgrimoire.com and caddy.reverse_proxy are properly configured for the exposed service.
-
Placement constraints:
- FAIL: The constraint
node.hostname == znasshould be reconsidered as it limits the service to a single node (znas). It may not be ideal if you want redundancy or failover capabilities. Fix: Consider using more flexible placement constraints that ensure the service is scheduled on suitable nodes without being tied to a specific hostname.
- FAIL: The constraint
-
Volumes use /DockerVol/ path convention:
- PASS: All volumes follow the convention, e.g.,
/DockerVol/kopia/config,/DockerVol/kopia/cache, etc.
- PASS: All volumes follow the convention, e.g.,
-
Network references external netgrimoire overlay:
- PASS: The service is correctly referencing an external network named
netgrimoire.
- PASS: The service is correctly referencing an external network named
VERDICT: FAIL
The primary issue identified is the placement constraint that limits the service to a single node, which may hinder redundancy and failover capabilities.