devops-infra_skill

Overview

This skill is a DevOps Infrastructure Agent that handles infrastructure management, scaling, backups, and network configuration for containerized applications. It provides commands, procedures, and runbook-style guidance for Docker resources, volumes, backups, and proxy/network management. The goal is reliable runtime operations, repeatable maintenance, and clear escalation steps for incidents.

How this skill works

The agent inspects and manages Docker resources (images, containers, volumes, networks) and host-level proxy configuration (Caddy). It automates routine maintenance tasks such as pruning unused resources, backing up databases and volumes, validating and reloading proxy config, and provides options for scaling via orchestration (Swarm/Kubernetes) and load balancers. It also defines regular maintenance cadence and emergency procedures for outages and resource exhaustion.

When to use it

• When disk usage or unused Docker resources need cleanup and reclamation
• When you need reliable database and volume backup or restore procedures
• When planning to scale a single-instance deployment to multiple nodes
• When validating, reloading, or troubleshooting the Caddy proxy configuration
• When responding to service outages, disk full events, or network failures

Best practices

• Schedule daily log checks, weekly resource pruning, and monthly DB backups
• Keep a small number of recent container images and prune older tags regularly
• Store backups off-host and verify restore procedures periodically
• Use network isolation per environment (dev/prod) and inspect Docker networks regularly
• Adopt orchestration (Kubernetes/Swarm) and a load balancer before scaling traffic

Example use cases

• Free up disk space by pruning unused images and removing stale container tags
• Create a consistent nightly PostgreSQL dump and rotate backups with dated filenames
• Backup a Docker volume by running a temporary container that archives volume contents
• Validate and reload Caddy configuration after TLS or routing updates
• Plan migration from single-host Docker to Kubernetes with load balancer and DB replication