Skip to content

feat!: upgrade jitsu to v2.14.0 - #97

Open
echozio wants to merge 6 commits into
mainfrom
update/jitsu-2.14.0
Open

feat!: upgrade jitsu to v2.14.0#97
echozio wants to merge 6 commits into
mainfrom
update/jitsu-2.14.0

Conversation

@echozio

@echozio echozio commented Aug 20, 2026

Copy link
Copy Markdown
Contributor
  • feat!: update jitsu to v2.14.0
  • fix: bind wait-for role to the operator service account
  • fix: create clickhouse metrics database before events-log init
  • fix: seed admin user via dedicated job
  • refactor: move clickhouse database creation to its own job
  • fix: resolve @prisma/client for the seed job

Resolves #96

echozio and others added 5 commits August 20, 2026 05:15
Jitsu v2.14.0 moves functions/profile builders to dedicated
functions-server deployments reconciled by a new mandatory operator
service, and connector syncs to Kubernetes CronJobs reconciled by
syncctl.

- add operator component (deployment, service, namespaced RBAC for the
  functions-server resources it manages)
- add profiles component (rotor image in profiles mode) scheduling
  Profile Builder runs
- wire FUNCTIONS_SERVER_URL_TEMPLATE into console, rotor and ingest
- add JWT_SECRET (now required by the console) to the token generator
- add syncctl CronJob-mode repository config and RBAC (cronjobs,
  secret updates)
- remove console googleSchedulerKey (Google Cloud Scheduler support
  was removed upstream)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The operator's waitFor initContainers run kubectl wait under the
operator's own service account.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Since Jitsu 2.14 the console's ClickHouse client pins its session to
the metrics database, so the console can no longer create the database
itself — every command, including the CREATE DATABASE bootstrap, fails
with UNKNOWN_DATABASE on a fresh install. Create it via the ClickHouse
HTTP interface in an initContainer of the event-log-init job instead.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Since Jitsu 2.14 the console no longer creates the seed user at
startup; it is only created by the console management CLI. Run it in a
job with the console's DATABASE_URL, JWT_SECRET and GLOBAL_HASH_SECRET
so the password hash matches what the console verifies at login.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Copilot AI balanced review requested due to automatic review settings August 20, 2026 07:17
@echozio echozio changed the title feat: upgrade jitsu to v2.14.0 feat!: upgrade jitsu to v2.14.0 Aug 20, 2026

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

The console image ships @prisma/client only inside the pnpm store
without a top-level node_modules link, so the bundled management CLI
cannot resolve it. Point NODE_PATH at the store entry.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@echozio
echozio force-pushed the update/jitsu-2.14.0 branch from 3f8f0de to b597e0b Compare August 20, 2026 08:35
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.

Possible chart update

2 participants