audit(gremlin): vikunja FAIL 2026-05-04

This commit is contained in:
traveler 2026-05-04 06:42:06 -05:00
parent 5c17e52e3b
commit 2781c16915

View file

@ -0,0 +1,42 @@
---
title: Audit - vikunja.yaml
description: Gremlin audit report 2026-05-04
published: true
date: 2026-05-04T11:42:06.014Z
tags: gremlin,audit
editor: markdown
dateCreated: 2026-05-04T11:42:06.014Z
---
# Audit Report — vikunja.yaml
**Date:** 2026-05-04
**File:** swarm/vikunja.yaml
**Type:** Docker Swarm
**Verdict:** FAIL
---
### Audit Results:
1. **Homepage Labels**:
- **PASS**: `homepage.group`, `homepage.name`, `homepage.icon`, `homepage.href`, `homepage.description` are present.
2. **Uptime Kuma Labels**:
- **FAIL**: No labels related to Uptime Kuma are found. Ensure that Uptime Kuma is included in the service definition and that appropriate labels are added.
3. **Caddy Labels on Exposed Services**:
- **PASS**: `caddy` label with domain and reverse proxy configuration is present for Vikunja service.
4. **Placement Constraints**:
- **PASS**: Constraint `- node.hostname == docker4` is applied to both services.
5. **Volumes Use /DockerVol/<service> Path Convention**:
- **PASS**: Volumes use the specified `/DockerVol/<service>` path convention for both Vikunja and Vikdb services.
6. **Network References External netgrimoire Overlay**:
- **PASS**: Both services reference the external `netgrimoire` network correctly.
### VERDICT: FAIL
The audit has identified a failure in the presence of Uptime Kuma labels, which are essential for monitoring and managing uptime of services within NetGrimoire. Ensure that Uptime Kuma is included in your swarm configuration and that appropriate labels are added for it to function correctly.