Pipeline: DIUN detects new image versions every 6h → webhook to n8n → n8n filters (skip databases/custom/infra/:latest) and rate-limits (max 5/6h) → SSH to dev VM → claude -p runs upgrade agent. Agent workflow: resolve GitHub repo → fetch changelogs → classify risk (SAFE/CAUTION) → backup DB if needed → bump version in .tf → commit+push → wait for CI → verify (pod ready + HTTP + Uptime Kuma) → rollback on failure. Changes: - stacks/n8n: add N8N_PORT=5678 to fix K8s env var conflict - stacks/n8n/workflows: version-controlled n8n workflow backup - docs/architecture/automated-upgrades.md: full pipeline documentation - AGENTS.md: add upgrade agent section - service-catalog.md: update DIUN description Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
5.5 KiB
5.5 KiB
Automated Service Upgrades
Overview
OSS services are automatically upgraded via a pipeline that detects new container image versions, analyzes changelogs for breaking changes, backs up databases, applies version bumps through Terraform, and verifies health post-upgrade with automatic rollback on failure.
Architecture
DIUN (every 6h)
│ detects new image tags
│
▼
n8n Webhook (POST /webhook/<uuid>)
│ filters: skip databases, custom images, infra, :latest
│ rate limit: max 5 upgrades per 6h window
│
▼
SSH → Dev VM (10.0.10.10)
│
▼
claude -p "upgrade agent prompt"
│
▼
Service Upgrade Agent
├── 1. Identify service + .tf files (grep stacks/)
├── 2. Resolve GitHub repo (config overrides + auto-detect)
├── 3. Fetch changelogs via GitHub API (authenticated, 5000 req/hr)
├── 4. Classify risk (SAFE / CAUTION / UNKNOWN)
├── 5. Slack notification — starting
├── 6. DB backup (if DB-backed service)
├── 7. Edit .tf files (version bump + config changes)
├── 8. Commit + push (Woodpecker CI applies)
├── 9. Wait for CI (poll Woodpecker API)
├── 10. Verify (pod ready + HTTP + Uptime Kuma)
├── 11a. SUCCESS → Slack report
└── 11b. FAILURE → git revert + CI re-applies → Slack alert
Components
DIUN (Docker Image Update Notifier)
- Stack:
stacks/diun/ - Schedule: Every 6 hours (
DIUN_WATCH_SCHEDULE=0 */6 * * *) - Role: Detection only — fires a webhook to n8n when a new image tag is found
- Skip patterns: Databases,
viktorbarzin/*,registry.viktorbarzin.me/*, infrastructure images - Webhook:
DIUN_NOTIF_WEBHOOK_ENDPOINTfrom Vaultsecret/diun→n8n_webhook_url
n8n Workflow ("DIUN Upgrade Agent")
- Stack:
stacks/n8n/ - Workflow backup:
stacks/n8n/workflows/diun-upgrade.json - Webhook path: UUID-based (
/webhook/<uuid>) - Filters:
- Only
status=update(skipnew,unchanged) - Skip databases, custom images, infra images,
:latest
- Only
- Rate limiting: Max 5 upgrades per 6-hour window using
$getWorkflowStaticData('global') - Action: SSH to dev VM, runs
claude -pwith the upgrade agent prompt
Upgrade Agent
- Prompt:
.claude/agents/service-upgrade.md - Config:
.claude/reference/upgrade-config.json - Contains:
- 50+ Docker image → GitHub repo mappings
- 22 Helm chart → GitHub repo mappings
- 27 DB-backed service definitions with backup metadata
- Skip patterns and breaking change keywords
Risk Classification
| Risk | Criteria | Verification | Version Jump |
|---|---|---|---|
| SAFE | Patch/minor bump, no breaking keywords in release notes | 2 minutes | Direct to target |
| CAUTION | Major bump, or breaking change keywords found, or in version_jump_always_step list |
10 minutes | Step through each version |
| UNKNOWN | Changelog unavailable | 2 minutes (SAFE defaults) | Direct to target |
Breaking change keywords: breaking, BREAKING, migration required, schema change, database migration, manual intervention, action required, removed, deprecated, renamed, incompatible
Database Backup
DB-backed services trigger a pre-upgrade backup automatically:
- Shared PostgreSQL:
kubectl create job --from=cronjob/postgresql-backup -n dbaas - Shared MySQL:
kubectl create job --from=cronjob/mysql-backup -n dbaas - Dedicated databases (e.g., Immich): Trigger existing backup CronJob in the service's namespace
If the backup fails, the upgrade is aborted.
Rollback
On verification failure:
git revert --no-edit <upgrade-commit-sha>git push→ Woodpecker CI re-applies the old version- Re-verify rollback succeeded
- If rollback also fails → CRITICAL Slack alert for manual intervention
Version Patterns
The agent handles all three version patterns in Terraform:
| Pattern | Example | Agent Action |
|---|---|---|
| Variable-based | variable "immich_version" { default = "v2.7.4" } |
Edit the default value |
| Hardcoded | image = "vaultwarden/server:1.35.4" |
Replace tag in image string |
| Helm chart | version = "2026.2.2" in helm_release |
Bump chart version |
Configuration
Excluding images (handled by DIUN + n8n)
- Databases:
*postgres*,*mysql*,*redis*,*clickhouse*,*etcd* - Custom:
viktorbarzin/*,registry.viktorbarzin.me/*,ancamilea/*,mghee/* - Infrastructure:
registry.k8s.io/*,quay.io/tigera/*,nvcr.io/*,reg.kyverno.io/* :latesttags
Rate limiting
- Max 5 upgrades per 6-hour DIUN scan cycle
- Counter resets when the window expires
- Configurable in the n8n "Filter and Rate Limit" code node
Services that always step through versions
- Authentik, Nextcloud, Immich (configured in
upgrade-config.json→version_jump_always_step)
Monitoring
- Slack: All upgrade events reported (start, success, failure, rollback)
- Git: Detailed commit messages with changelog summaries, risk level, backup status
- DIUN Slack: Independent Slack channel for raw version detection (separate from upgrade agent)
Secrets
| Secret | Vault Path | Purpose |
|---|---|---|
| n8n webhook URL | secret/diun → n8n_webhook_url |
DIUN → n8n trigger |
| GitHub PAT | secret/viktor → github_pat |
Changelog fetch (5000 req/hr) |
| Slack webhook | secret/platform → alertmanager_slack_api_url |
Upgrade notifications |
| Woodpecker token | secret/viktor → woodpecker_token |
CI pipeline polling |