Use OBI v0.10.0 and align component versions#135
Merged
Conversation
paweljw
force-pushed
the
pawel/use-obi-0.10.0
branch
3 times, most recently
from
July 1, 2026 08:49
cea4d10 to
b27ab1b
Compare
- ebpf: bump OBI v0.7.1 -> v0.10.0; collector version -> 1.1.28 - collector: build the cluster-agent from source with the same statement_timeout patch as ebpf (v1.6.1) instead of pulling the stock 1.2.4 image. The stock image lacks the patch, so cluster-mode database monitoring could hit the PgBouncer statement_timeout rejection. - pin all Debian bases to 13.5 (trixie): obi-source was leftover on bookworm 12.11, and the builders floated on the trixie tag while the final was pinned -- a CGO glibc-skew risk for node-agent. - true up drifted version metadata (collector ENV OBI_VERSION, CLAUDE.md Node Agent/Debian/cluster-agent) against the Dockerfile pins. - add a version-sync CI check that fails when the pins, the collector ENV block, and the CLAUDE.md summary disagree (component versions + Debian).
paweljw
force-pushed
the
pawel/use-obi-0.10.0
branch
from
July 1, 2026 09:14
b27ab1b to
5a2d5c3
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps OBI eBPF instrumentation from v0.7.1 to v0.10.0, then fixes version metadata that had drifted from the Dockerfiles and adds CI to keep it honest.
OBI
ebpf/Dockerfile: OBI v0.7.1 → v0.10.0 (both arch tarballs verified to resolve)collector/Dockerfile: collector version → 1.1.28Cluster-agent drift (real fix)
The collector pulled the stock
coroot-cluster-agent:1.2.4while the ebpf image buildsv1.6.1from source with thestatement_timeoutDSN patch. In cluster-collector mode the collector's agent does database monitoring, so the stock image could reintroduce the PgBouncerstatement_timeoutrejection the patch fixes.collector/Dockerfilenow builds the cluster-agent from source with the same patch as ebpf (v1.6.1); the patch stays a single source of truth inebpf/patches/cluster-agent/.Debian bases
All Debian bases are now pinned to 13.5 (trixie):
12.11-slim(only a tar-extraction stage, but inconsistent) →13.5-slimtrixietag while the final was pinned13.5-slim. node-agent isCGO_ENABLED=1(glibc-linked), so a floating builder could out-run the pinned final's glibc. Builders (ebpf ×2 + the new collector one) → pinneddebian:13.5.Metadata true-up
collector/Dockerfile:ENV OBI_VERSION0.4.1 → 0.10.0,CLUSTER_AGENT_VERSION1.2.4 → 1.6.1CLAUDE.md: Node Agent 1.27.0 → 1.30.0, Debian 12.11 → 13.5, Cluster Agent 1.2.4 → 1.6.1; dropped the stale Debian version from the ebpf comment; added a keep-in-sync noteCI
.github/workflows/version-sync.ymlfails when the Dockerfile pins, the collectorENV *_VERSIONblock, and the CLAUDE.md summary disagree — Vector, OBI, Node Agent, Cluster Agent, and a single pinned Debian version across all stages. Verified green on the current tree and red on injected drift (including a reintroduced floatingtrixie).