chore(#227): bump greenfield ingestor baseline to v0.3.6#228
Merged
Conversation
The chart's pinned ingestor baseline was frozen at v0.3.2 (#184) and never bumped through 0.3.3–0.3.6, so fresh installs and `helm upgrade` re-assert v0.3.2 — which lacks data-ingestors#150 (missing values flagged as "non-numeric"). A customer (Opentarget) hit exactly this on fresh namespace installs and after `helm upgrade`. Bump the baseline digest to v0.3.6 (ghcr ingestor:0.3.6, multi-arch amd64+arm64) and the chart version 1.5.0 → 1.5.1 in lockstep. Fresh installs and upgrades now land on the fixed image; ongoing rollouts remain managed by image-refresh. Does not address the separate image-refresh silent-skip issue (#190). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
|
👋 Heads-up — Code review queue is at 9 / 8 Above the WIP limit. The team convention is to review existing PRs before opening new work. Open PRs currently in Code review (oldest first):
Pull from review before opening new work. (This is a nudge from the kanban WIP check, not a block.) |
LukasWodka
approved these changes
Jun 8, 2026
5 tasks
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
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.
Why
A customer (Opentarget / Henrik) reported the data ingestor still hitting the "empty cells flagged as non-numeric" error — that's
tracebloc/data-ingestors#150, fixed in v0.3.3. Root cause: the chart's greenfield ingestor baseline is frozen at v0.3.2.images.ingestor.digest: sha256:d361fa77…is exactlyghcr.io/tracebloc/ingestor:0.3.2(verified on ghcr).0.3tag auto-refreshes running deployments, but the baseline still wins on fresh installs (run 0.3.2 for ~15–30 min before converging) and onhelm upgrade(re-asserts the baseline) — exactly the customer's situation (new namespace + upgrades).What
client/values.yamlimages.ingestor.digest→sha256:dfdaa7e6…(ingestor:0.3.6, multi-arch amd64+arm64); comment updated with the cumulative 0.3.3→0.3.6 fixesclient/Chart.yamlversion+appVersion1.5.0 → 1.5.1Fresh installs and
helm upgradenow land on the fixed v0.3.6 image. The new digest is a multi-arch index, so theingestor-multiarchCI guard stays green. Precedent: #161 (v0.3.0→v0.3.1), #185 (v0.3.1→v0.3.2).Closes #227.
Not in this PR
helm upgrade <release> tracebloc/client -n <ns> --reuse-values --set images.ingestor.digest=sha256:dfdaa7e633a8df0f46b403e9422eba5c16bdb7d9c39047e6d3738f9e38fbdba8.Note for reviewers
Release-gated chart change — needs a second approver (no self-approve), and the chart must be promoted/published (develop→main) before customers can
helm upgradeonto 1.5.1.🤖 Generated with Claude Code
Note
Low Risk
Release-only digest and version pinning in the Helm chart; no runtime logic changes in this repo, with the new digest remaining a multi-arch index per existing CI expectations.
Overview
Bumps the client Helm chart to 1.5.1 and moves the greenfield
images.ingestor.digestbaseline from ingestor v0.3.2 to v0.3.6 (sha256:dfdaa7e6…), so fresh installs andhelm upgradestart jobs-manager with the fixed ingestor image instead of staying on the stale pin.The
values.yamlcomment is updated to document why the jump skips 0.3.3–0.3.5 (cumulative NULL/empty-cell ingestion fixes, including data-ingestors#150). The floatingimages.ingestor.tag: "0.3"is unchanged; only the explicit baseline digest and chart version move forward.Reviewed by Cursor Bugbot for commit 5c5284c. Bugbot is set up for automated code reviews on this repo. Configure here.