The latest articles on DEV Community by Priyank Singh (@priyank_singh). https://dev.to/priyank_singh https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4031250%2F56eb6e24-7893-44c9-9e50-495e0fe5a7b1.png https://dev.to/priyank_singh en Priyank Singh Thu, 16 Jul 2026 03:36:18 +0000 https://dev.to/jitsucom/jitsu-2140-moving-to-kubernetes-native-self-hosting-4f8j https://dev.to/jitsucom/jitsu-2140-moving-to-kubernetes-native-self-hosting-4f8j <p><strong>Jitsu 2.14.0: Kubernetes-native self-hosting, Function Servers, and CronJob-based syncs</strong></p> <p>Jitsu 2.14.0 is now available.</p> <p>This is our first stable release since jitsu2-v2.11.0 in August 2025, bringing together roughly 1,600 commits across the platform.</p> <p>The biggest change is architectural: Jitsu is now Kubernetes-native for feature-complete production self-hosting.</p> <h2> Why we made this change </h2> <p>In earlier versions, several important runtime components were still tied to older deployment assumptions.</p> <p>User functions, profile builders, and connector syncs needed a cleaner operational model to scale reliably in self-hosted environments.</p> <p>In 2.14.0, these components now run as first-class Kubernetes workloads.</p> <h2> Function Servers </h2> <p>User functions and Profile Builder v2 now run on dedicated Function Servers.</p> <p>A new Jitsu operator manages the Kubernetes resources required for each deployment.</p> <p>This gives us a stronger foundation for:</p> <ul> <li>workload isolation</li> <li>autoscaling</li> <li>sharding</li> <li>different execution classes</li> <li>more reliable production operations</li> <li>CronJob-based connector syncs</li> </ul> <p>Connector syncs have moved from Google Cloud Scheduler to Kubernetes CronJobs.</p> <p>syncctl now reconciles scheduled syncs directly into the cluster. Each sync runs as an independent pod with its configuration stored in Kubernetes.</p> <p>This removes a cloud-specific dependency and makes production self-hosting more portable.</p> <h2> What else is included </h2> <p>This release also adds:</p> <ul> <li>MCP server support in Jitsu Console</li> <li>generated OpenAPI specifications and API reference</li> <li>user API tokens</li> <li>audit logs</li> <li>maintenance mode</li> <li>dead-letter queues and event reprocessing</li> <li>improved sync and connection notifications</li> <li>a redesigned signup flow</li> <li>ClickHouse TTL-based event-log retention</li> <li>development Helm charts</li> <li>new and improved integrations</li> <li>Important upgrade notes</li> </ul> <h2> This release includes breaking changes. </h2> <p>Kubernetes is now required for production deployments using functions, profile builders, or connector syncs.</p> <p>Docker Compose is deprecated for complete production deployments and is now intended primarily for local development and exploration.</p> <h2> Try it and help us improve </h2> <p>We are actively investing in Jitsu again and would love feedback from developers, data engineers, and teams running event infrastructure in production.</p> <p>Try the release, test the self-hosting experience, open an issue, or tell us what feels confusing, incomplete, or unnecessarily difficult.</p> <p>We are especially interested in feedback around:</p> <ul> <li>Kubernetes deployment and upgrades</li> <li>connector reliability</li> <li>event observability</li> <li>function execution</li> <li>developer experience</li> <li>documentation</li> </ul> <p>Release notes: <a href="https://github.com/jitsucom/jitsu/releases/tag/2.14.0" rel="noopener noreferrer">Jitsu 2.14.0 on GitHub</a></p> <p>Self-hosting documentation: <a href="https://docs.jitsu.com/self-hosting" rel="noopener noreferrer">Jitsu self-hosting guide</a></p> <p>Jitsu is open source, and we would love your help making it better.</p> opensource dataengineering analytics dataplatform