kuberik
DocsBlog
CTRL K
    GitHub Get started
    CTRL K
      • Docs home

      Get started

      • What Is Kuberik
      • Install
        • Install with Helm
        • Install with kubectl
        • Set Up Dashboard Sign-in
      • Deploy Your First App

      Concepts

      • How Kuberik Works
      • Rollouts
      • Environments
      • Propagation Modes
      • How Gates Work

      Ship Releases

      • Publish Releases from CI
      • Promote Across Environments
      • Define the Pipeline Once
      • Roll Out with a Canary

      Gate Deploys

      • Verify with Health Checks
      • Require a Manual Approval
      • Set Deployment Windows
      • Wait for Service Dependencies

      Operate

      • Use the Dashboard
      • Operate with kubectl
      • Monitor Rollouts
      • Troubleshoot

      Integrations

      • Flux
      • GitHub
      • Datadog
      • Prometheus

      Reference

      • API Reference
      • Annotations

      Kuberik

      • kuberik.com
      • Blog
      • GitHub

      Ship Releases

      Publish releases from CI and move them through your environments.

      • Publish Releases from CI Tag images or manifest artifacts in CI so a ReleaseSource picks them up.
      • Promote Across Environments Deploy to production only after staging has shipped the same release.
      • Define the Pipeline Once Write an app's Kuberik objects once in a kustomize component, and give each environment an overlay that sets only what differs.
      • Roll Out with a Canary Shift traffic to a new version in steps, with a bake time and a test Job holding each step.
      Previous How Gates Work Next Publish Releases from CI
      kuberik

      Open source under Apache 2.0.
      © 2026 the Kuberik authors.

      Product

      GatesCanary and wavesHealth checksGitOpsDashboardReleasesRollback

      Docs

      InstallDeploy your first appConceptsShip releasesGate deploysOperateIntegrationsAPI reference

      Community

      GitHubIssuesBlog