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

      Gate Deploys

      Hold a deploy until health checks, people, time windows or other services allow it. How Gates Work explains how they combine.

      • Verify with Health Checks Fail a deploy when the app is unhealthy during bake time.
      • Require a Manual Approval Hold each new build of a Rollout until a person approves it in the dashboard or with kubectl.
      • Set Deployment Windows Allow or deny deploys by time of day, day of week or date range.
      • Wait for Service Dependencies Hold a service until the service it needs has shipped a compatible version.
      Previous Roll Out with a Canary Next Verify with Health Checks
      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