Port Prometheus to local container build #262

Merged
eblume merged 2 commits from feature/prometheus-local-container into main 2026-02-24 09:15:57 -08:00
Owner

Summary

  • Add three-stage Dockerfile for Prometheus v3.9.1 (Node UI → Go binaries → Alpine runtime)
  • Produces prometheus and promtool binaries with embedded web UI assets
  • Follows navidrome/ntfy pattern for supply chain control via Zot registry

Deployment and Testing

  • dagger call build --src=. --container-name=prometheus succeeds
  • Container reports correct version via prometheus --version
  • promtool --version works
  • Update statefulset image reference after successful build
  • Deploy from branch: argocd app set prometheus --revision <branch> && argocd app sync prometheus
  • Health probes pass (/-/healthy, /-/ready)
  • Web UI loads, scrape targets work, remote write functions
## Summary - Add three-stage Dockerfile for Prometheus v3.9.1 (Node UI → Go binaries → Alpine runtime) - Produces `prometheus` and `promtool` binaries with embedded web UI assets - Follows navidrome/ntfy pattern for supply chain control via Zot registry ## Deployment and Testing - [ ] `dagger call build --src=. --container-name=prometheus` succeeds - [ ] Container reports correct version via `prometheus --version` - [ ] `promtool --version` works - [ ] Update statefulset image reference after successful build - [ ] Deploy from branch: `argocd app set prometheus --revision <branch> && argocd app sync prometheus` - [ ] Health probes pass (`/-/healthy`, `/-/ready`) - [ ] Web UI loads, scrape targets work, remote write functions
Three-stage build: Node (UI assets), Go (prometheus + promtool binaries),
Alpine runtime. Follows navidrome/ntfy pattern for supply chain control.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
registry.ops.eblu.me/blumeops/prometheus:v3.9.1-74029e1

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
eblume merged commit 2ba5d8a8aa into main 2026-02-24 09:15:57 -08:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
eblume/blumeops!262
No description provided.