A cluster group allows you to define logical sets of clusters (e.g., “US-East prod,” “EU staging”). Deployments can then target groups with a single configuration. Combined with the new visualization, teams can execute sophisticated canary releases across different cloud providers or on-prem clusters without writing custom service mesh rules by hand.
With the release of , the project isn't just adding features—it's signaling a clear maturation toward enterprise-scale GitOps, multi-cluster resilience, and what the team calls “environment as code.” The Headline: GitOps is No Longer an Add-On Earlier versions of Zadig offered GitOps as a pattern you could implement if you knew the YAML incantations. Zadig 2.5 makes GitOps a first-class primitive. zadig 2.5
In the crowded landscape of CI/CD and application delivery platforms, few have managed to balance developer experience with the raw complexity of Kubernetes-native deployment. Zadig, the open-source platform born from KodeRover, has been quietly building a reputation as a bridge between traditional Jenkins pipelines and modern, GitOps-driven workflows. A cluster group allows you to define logical
The new allows teams to define the entire delivery process—from commit to production—inside Git repositories. Changes to deployment manifests, Helm charts, or Kustomize overlays trigger reconciliations directly in the target clusters. More importantly, Zadig 2.5 introduces a bidirectional synchronization state: drift between the Git source of truth and the live cluster is now visualized directly in the UI, with one-click remediation. With the release of , the project isn't
For now, 2.5 is worth a spin in a staging cluster—especially if your team has been struggling to make GitOps accessible beyond the core platform team. Zadig 2.5 is available under the Apache 2.0 license. For installation and release notes, see github.com/koderover/zadig .