Skip to content

chore(#227): bump greenfield ingestor baseline to v0.3.6#228

Merged
saadqbal merged 1 commit into
developfrom
chore/pin-ingestor-v0.3.6-227
Jun 8, 2026
Merged

chore(#227): bump greenfield ingestor baseline to v0.3.6#228
saadqbal merged 1 commit into
developfrom
chore/pin-ingestor-v0.3.6-227

Conversation

@saadqbal

@saadqbal saadqbal commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

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 exactly ghcr.io/tracebloc/ingestor:0.3.2 (verified on ghcr).
  • Pinned 2026-06-03 (Pin greenfield ingestor baseline to v0.3.2 in client chart #184), never bumped across 0.3.3 / 0.3.4 / 0.3.5 / 0.3.6 (RELEASING.md step 7 made optional in data-ingestors#144).
  • The floating 0.3 tag auto-refreshes running deployments, but the baseline still wins on fresh installs (run 0.3.2 for ~15–30 min before converging) and on helm upgrade (re-asserts the baseline) — exactly the customer's situation (new namespace + upgrades).

What

File Change
client/values.yaml images.ingestor.digestsha256:dfdaa7e6… (ingestor:0.3.6, multi-arch amd64+arm64); comment updated with the cumulative 0.3.3→0.3.6 fixes
client/Chart.yaml version + appVersion 1.5.0 → 1.5.1

Fresh installs and helm upgrade now land on the fixed v0.3.6 image. The new digest is a multi-arch index, so the ingestor-multiarch CI guard stays green. Precedent: #161 (v0.3.0→v0.3.1), #185 (v0.3.1→v0.3.2).

Closes #227.

Not in this PR

  • image-refresh: surface persistent ingestor (ghcr) digest-resolve failures instead of silently skipping #190 (image-refresh silently skipping when the ghcr digest can't resolve) — if the customer's on-prem cluster can't reach ghcr.io, auto-refresh never rolls forward and he'd be permanently stuck on the baseline. Needs his cluster diagnostics; tracked separately.
  • Immediate customer unblock (independent of this chart release): 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 upgrade onto 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.digest baseline from ingestor v0.3.2 to v0.3.6 (sha256:dfdaa7e6…), so fresh installs and helm upgrade start jobs-manager with the fixed ingestor image instead of staying on the stale pin.

The values.yaml comment 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 floating images.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.

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>
@LukasWodka

Copy link
Copy Markdown
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.)

@saadqbal saadqbal merged commit 6f2a70a into develop Jun 8, 2026
18 checks passed
saadqbal added a commit that referenced this pull request Jun 8, 2026
…230)

chore(#227): bump greenfield ingestor baseline to v0.3.6
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.

2 participants