audit(gremlin): beszel_agents FAIL 2026-04-27

This commit is contained in:
traveler 2026-04-27 06:07:27 -05:00
parent 45e67c472e
commit 2b55b3da2f

View file

@ -0,0 +1,47 @@
---
title: Audit - beszel_agents.yaml
description: Gremlin audit report 2026-04-27
published: true
date: 2026-04-27T11:07:27.254Z
tags: gremlin,audit
editor: markdown
dateCreated: 2026-04-27T11:07:27.254Z
---
# Audit Report — beszel_agents.yaml
**Date:** 2026-04-27
**File:** swarm/beszel_agents.yaml
**Type:** Docker Swarm
**Verdict:** FAIL
---
### Audit Summary:
1. **Homepage labels**:
- The `beszel_agents.yaml` file does not include any homepage labels (`homepage.group`, `homepage.name`, `homepage.icon`, `homepage.href`, `homepage.description`). These are typically used in documentation or UI configurations.
**Action:** Add these labels to your configuration for better visibility and documentation.
2. **Uptime Kuma labels**:
- The configuration does not include any Uptime Kuma labels (`kuma.<n>.http.name`, `kuma.<n>.http.url`).
**Action:** If you are using Uptime Kuma, add the necessary labels to your configuration.
3. **Caddy labels on exposed services**:
- Caddy configuration is not visible in this file. Ensure that any services exposing HTTP/HTTPS endpoints have appropriate Caddy configurations with reverse proxy settings.
4. **Placement constraints**:
- The `node.hostname` placement constraint is correctly used for each service. For example, `docker2`, `docker3`, etc., are specified as required nodes.
**Action:** Verify that the specified node hostnames (`docker2`, `docker3`, etc.) exist in your Docker Swarm environment.
5. **Volumes use `/DockerVol/<service>` path convention**:
- The volumes specified do not follow the `/DockerVol/<service>` path convention. For instance, `/var/run/docker.sock` is used directly.
**Action:** Update the volume paths to match the specified convention (e.g., `/DockerVol/beszel-agent-docker2/var/run/docker.sock`).
6. **Network references external `netgrimoire` overlay**:
- The network `netgrimoire` is referenced correctly as an external network in the configuration.
**Action:** Ensure that this network exists on your Docker Swarm and has the necessary configurations.
### VERDICT: FAIL
The configuration does not include essential labels for documentation, uses incorrect volume paths, and requires updates to meet specified conventions and constraints.