audit(gremlin): Calibre-web FAIL 2026-04-03

This commit is contained in:
traveler 2026-04-02 20:42:48 -05:00
parent 33d47b50fd
commit 8191b0aee6

View file

@ -2,10 +2,10 @@
title: Audit - Calibre-web.yaml
description: Gremlin audit report 2026-04-03
published: true
date: 2026-04-03T01:32:54.327Z
date: 2026-04-03T01:42:48.069Z
tags: gremlin,audit
editor: markdown
dateCreated: 2026-04-03T01:32:54.327Z
dateCreated: 2026-04-03T01:42:48.069Z
---
# Audit Report — Calibre-web.yaml
@ -17,26 +17,31 @@ dateCreated: 2026-04-03T01:32:54.327Z
---
1. **Homepage labels**:
- **PASS**: homepage.group, homepage.name, homepage.icon, homepage.href, homepage.description are all present.
1. **Homepage labels**:
- `homepage.group`: PASS
- `homepage.name`: PASS
- `homepage.icon`: PASS
- `homepage.href`: PASS
- `homepage.description`: PASS
2. **Uptime Kuma labels**:
- **FAIL**: Missing `kuma.cwa.http.name` and `kuma.cwa.http.url`. These should be added to ensure proper monitoring in Uptime Kuma.
- `kuma.cwa.http.name`: PASS
- `kuma.cwa.http.url`: PASS
3. **Caddy labels on exposed services**:
- **PASS**: caddy=books.netgrimoire.com , books.pncharris.com and caddy.reverse_proxy are correctly set.
- `caddy`: PASS
- `caddy.reverse_proxy`: PASS
4. **Placement constraints**:
- **FAIL**: `node.hostname == znas` constraint should be reviewed as it may not apply to all nodes. Ensure this is correct for your environment.
- `node.hostname == znas`: PASS
5. **Volumes use /DockerVol/<service> path convention**:
- **PASS**: All volumes follow the `/DockerVol/Calibre-web/Config`, `/data/nfs/znas/Data/media/books/library/Netgrimoire` conventions.
- `/DockerVol/Calibre-web/Config`: PASS
- `/data/nfs/znas/Data/media/books/library/Netgrimoire`: FAIL (This volume does not follow the `/DockerVol/<service>` path convention)
6. **Network references external netgrimoire overlay**:
- **PASS**: The service correctly references an external network `netgrimoire`.
- `netgrimoire`: PASS
**VERDICT: FAIL**
Explanation for the FAIL items:
- Uptime Kuma labels are missing essential keys that prevent proper monitoring.
- Placement constraints should be carefully reviewed to ensure they align with your cluster's architecture.
The Calibre-web service uses a volume that does not follow the specified naming convention, which could lead to misconfiguration or conflicts in managing volumes across different services.