What is Kuberik
Kuberik is a Kubernetes-native delivery orchestrator. It takes over after your CI publishes a new version — a container image or rendered manifests — and handles everything that happens next: safe rollout, verification, and promotion.
You Release, Kuberik Delivers
| Owner | Example | |
|---|---|---|
| When to release | You (developer/CI) | Push a git tag, merge to main |
| How to deliver | Kuberik | Rollout, verify health, promote across environments |
Your CI pipeline publishes a tagged artifact: the application image itself, or the rendered manifests for an environment pushed as an OCI artifact. Kuberik detects the new tag and orchestrates the delivery — gating, deploying, verifying, and promoting — without any further input from you. See Propagation Modes for how the two modes compare.
Kuberik does not build images, decide when to release, or replace your GitOps tool. It works alongside FluxCD at the application delivery layer.
How It Works
Publish
Your CI publishes a tagged image or manifest artifact to a container registry.
Detect
FluxCD detects the new tag via ImagePolicy.
Gate
Kuberik creates a release candidate and evaluates gates.
Deploy
Kuberik writes the version into the Kustomization, or moves the OCIRepository tag to the new manifests.
Verify
Health checks verify the deployment during bake time.
Complete
The release is marked as succeeded or failed.
For a detailed component breakdown, see Architecture.