blumeops/argocd/manifests/tempo/kustomization.yaml
Erich Blume 75f9ba4943
All checks were successful
Build Container / detect (push) Successful in 2s
Build Container / build-dockerfile (tempo) (push) Successful in 6s
Build Tempo container from source (2.10.3) (#323)
## Summary
- Add `containers/tempo/Dockerfile` — two-stage Go build from forge mirror, modeled on loki
- Switch kustomization from upstream `grafana/tempo` to `registry.ops.eblu.me/blumeops/tempo`
- Bump Tempo 2.10.1 → 2.10.3

## Test plan
- [ ] Kick off container build via `mise run container-build-and-release tempo`
- [ ] Update kustomization `newTag` with built image tag
- [ ] Deploy from branch: `argocd app set tempo --revision local-tempo-container && argocd app sync tempo`
- [ ] Verify Tempo health: `curl tempo.ops.eblu.me/ready`
- [ ] Verify traces flowing in Grafana Tempo datasource

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Reviewed-on: #323
2026-04-02 13:45:02 -07:00

20 lines
382 B
YAML

apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
namespace: monitoring
resources:
- statefulset.yaml
- service.yaml
- ingress-tailscale.yaml
- ingress-tailscale-otlp.yaml
images:
- name: grafana/tempo
newName: registry.ops.eblu.me/blumeops/tempo
newTag: "v2.10.3-49ce545"
configMapGenerator:
- name: tempo-config
files:
- tempo.yaml