JITSU-48: rename the Helm chart from jitsu-dev to jitsu

[sahiltyagi-jitsu]

JITSU-48 asks whether the chart should keep the jitsu-dev identity now that it is what self-hosters are pointed at. Ildar's answer on the thread was one word: rename.

Split out from the prod-mode work (#NEXT) so a naming decision is reviewable on its own rather than buried in ~600 lines of templating.

What changed

Chart.yaml name and description, the jitsu-dev.* template helpers → jitsu.*, and the two sentences of prose that called it "the development Helm chart".

Everything else in the diff is the helper prefix.

Why jitsu

Ildar's own precedent, not a preference of mine. He created jitsu-dev in Feb 2026 (26fcf6665). In July he extracted the dependencies into a sibling chart and named it jitsu-deps — not jitsu-deps-dev — in ee0d3a8b4, even though that chart is equally dev-only. git log -p shows jitsu-deps is the only name it has ever had.

Three further confirmations in-repo: RELEASE_NAME already defaults to jitsu (dev-deploy.sh:13), the common labels already emit app.kubernetes.io/part-of: jitsu, and the sibling release is jitsu-deps.

Nothing external depends on the old name

Verified: no workflow under .github/ mentions helm at all; there is no helm package, helm push, chart-releaser, index.yaml or chart repository anywhere in the repo. The chart is consumed one way — clone and run helm/dev-deploy.sh, which passes CHART_DIR="$SCRIPT_DIR", a path, never a chart name.

So there is no published artifact to rename and no consumer pinning jitsu-dev.

It cannot break an existing install

Helm keys a release on the release name, not the chart name.

Rendered output, before vs after: the only differences are # Source: comments and the helm.sh/chart label. Resource names and app.kubernetes.io/name selector labels are byte-identical (md5 match) — the templates hardcode name: console etc. and never derive names from the chart, so the immutable-selector failure a rename usually risks does not apply.

Confirmed against a live cluster, not just the diff: helm upgrade took a Minikube release from jitsu-dev-0.1.0 (revision 6) to jitsu-0.1.0 (revision 7) with no resource recreated. Only console and operator rolled new pods — the two whose pod templates genuinely changed in later commits; the other five kept pods that were 3d22h old.

Deliberately not included

• appVersion: "dev" — read by nothing (it appears twice in the repo, once per Chart.yaml, referenced by no template, label or workflow), and helm-deps carries the same value, so changing one alone creates a fresh inconsistency. Giving the chart a real version implies a release process that does not exist.
• CHANGES.md still says "development Helm chart" in three places. It is a changelog describing a past release; rewriting history there would be wrong.

Scope note

Two other matches for jitsu-dev in the repo are unrelated and untouched: jitsu-dev-network in docker/docker-compose.yml is a Docker network name, and the three in helm-deps/values.yaml are dev passwords. A repo-wide rename would have changed both.

🤖 Generated with Claude Code

[jitsu-code-review]

Reviewed the Helm chart identity and helper rename, including rendered manifests and upgrade-sensitive labels/selectors. No actionable findings.