fix(chart): bump default ingestor tag 0.3 → 0.5

[divyasinghds]

What

Bumps the default spawned-ingestor float tag images.ingestor.tag from 0.3 → 0.5.

Why

jobs-manager validates every ingest.yaml at submit time against a vendored schema that now tracks data-ingestors' newer task categories — sentence_pair_classification, embeddings, seq2seq, causal_language_modeling (client-runtime#162). Those categories first ship in the ingestor 0.5 line (v0.5.6); the 0.3 float tag resolves to the latest 0.3.x (v0.3.12), which supports only 11 categories.

Leaving the spawned ingestor on 0.3 while submit-time validation accepts 15 re-opens the submit-vs-run drift bug (the #64 class): a customer submitting one of the new categories passes validation, a Job is minted, and the 0.3 image can't process it. This was found while triaging review comments on client-runtime#161 — dev, staging, and prod all pin 0.3.

Changes

• values.yaml — images.ingestor.tag 0.3 → 0.5, with a rationale comment. 0.5 auto-tracks 0.5.x patches (imagePullPolicy=Always); a future 0.6 needs an explicit bump, same convention as before.
• templates/jobs-manager-deployment.yaml — the --reuse-values nil-guard fallback default "0.3" → default "0.5", so upgrading a release that predates the images.ingestor key doesn't silently fall back to the drifting 0.3.
• tests/jobs_manager_test.yaml — default-wiring assertion 0.3 → 0.5.

Verification

helm template renders INGESTOR_IMAGE_TAG: "0.5" on both the default path and the nil-guard (images.ingestor=null) path.

Before merge / deploy — please confirm

• ghcr.io/tracebloc/ingestor:0.5 exists and is a multi-arch index (amd64+arm64). Per release-image.yml the v0.5.x releases publish the :0.5 float tag; the chart's ingestor-multiarch CI job enforces the multi-arch requirement. (I couldn't list ghcr tags directly — the CLI token lacks read:packages.)
• Roll this out before or with the client-runtime develop→staging promotion (client-runtime#161), so staging's submit schema never gets ahead of the ingestor it schedules.

Related

• client-runtime#162 (schema → develop, 15 categories)
• client-runtime#161 (staging promotion; review flagged this drift)

🤖 Generated with Claude Code

---

Note

Medium Risk
Changes which container image runs for all default ingestion Jobs; wrong or missing ghcr.io/tracebloc/ingestor:0.5 would break ingestion fleet-wide, but scope is a version bump aligned with runtime schema—not auth or data-path logic.

Overview
Aligns the chart’s default spawned ingestor with jobs-manager validation by changing images.ingestor.tag from 0.3 to 0.5, with comments explaining that newer task categories (e.g. sentence_pair_classification, embeddings) ship on the 0.5 line while 0.3 only covered 11 categories.

The jobs-manager deployment template’s nil-guard fallback for INGESTOR_IMAGE_TAG is updated the same way (0.3 → 0.5), so upgrades with --reuse-values on releases that lack images.ingestor no longer silently schedule the old 0.3 image. The Helm unit test for default ingestor wiring expects 0.5 instead of 0.3.

^{Reviewed by Cursor Bugbot for commit 7268b24. Bugbot is set up for automated code reviews on this repo. Configure here.}