Skip to content

build: bump Prometheus, Grafana and Jaeger to their latest minors - #61

Merged
AlpNuhoglu merged 2 commits into
mainfrom
build/monitoring-image-bumps
Oct 19, 2026
Merged

AlpNuhoglu merged 2 commits into
mainfrom
build/monitoring-image-bumps

Conversation

@AlpNuhoglu

Copy link
Copy Markdown
Owner

Same three bumps as Dependabot's grouped PR #59 (Prometheus v2.55.1, Grafana 11.6.16, Jaeger 1.76.0; same digests, each checked against the registry tag and multi-platform incl. amd64/arm64), applied on the paths A8 (#60) moved them to. #59 is stuck: it targets the old 30-monitoring.yaml and conflicts; Dependabot's run after #60 computed the same changes on the new paths and logged "Creating a pull request for 'third-party-images'", but neither opened a new PR nor rewrote #59. Once this merges the dependencies are current and Dependabot should close #59. The collector stays at 0.111.0 (ignored, Bulgu #71).

Measured:

  • k3d (monitoring component, restricted profile): Grafana 11.6.16 database ok, groups=472 only; Prometheus 2.55.1 scrapes 14/14 targets.
  • docker-compose: Prometheus ready, Grafana ok, Jaeger 1.76 healthy and receiving traces from six services.
  • Trivy HIGH/CRITICAL with a fix: Grafana 141 → 74 and off end-of-life Alpine 3.19 (now 3.24); Jaeger 76 → 73 and off end-of-life Alpine 3.20 (now 3.22); Prometheus 112 → 108. Majors remain Bulgu docs(plan): first production deploy (B4) #68.

Refs: Bulgu #68

🤖 Generated with Claude Code

AlpNuhoglu and others added 2 commits October 19, 2026 15:37
Dependabot's grouped PR #57 proposes Prometheus v2.55.1, Grafana
11.6.16 and Jaeger 1.76.0, but in the manifest path that A8 moves
(30-monitoring.yaml), and it still carries the linux/386-only
collector tag that the new ignore rule no longer proposes; commenting
@dependabot recreate was acknowledged and started no update job. The
same three bumps are applied here on the new paths, with the digests
from #57, each checked against the registry tag and multi-platform
(amd64 and arm64 included). The collector stays at 0.111.0.

Measured:
- k3d (monitoring component, restricted profile): Grafana 11.6.16
  database ok, still running with groups=472 only; Prometheus 2.55.1
  scrapes 14 of 14 targets.
- docker-compose: Prometheus ready, Grafana ok, Jaeger 1.76 healthy and
  receiving traces from six services.
- Trivy (HIGH/CRITICAL with a fix): Grafana 141 -> 74 and off
  end-of-life Alpine 3.19 (now 3.24); Jaeger 76 -> 73 and off
  end-of-life Alpine 3.20 (now 3.22); Prometheus 112 -> 108. The major
  upgrades remain finding #68.

Refs: Bulgu #68

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Refs: Bulgu #68

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@AlpNuhoglu
AlpNuhoglu merged commit 72c3279 into main Oct 19, 2026
26 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant