GitOps-Native Deployments
Self-service that respects your Git-based workflows. Three deployment modes, enforced per service.
The Challenge
"We use ArgoCD for all our deployments. I need manifests pushed to Git, not deployed directly to the cluster. But I still want developers to have a simple UI.
GitOps requires all changes to flow through Git. Traditional self-service platforms break this model. You need per-service control over how deployments happen.
GitOps Integration
Knodex supports three deployment modes (Direct, GitOps, and Hybrid), enforced per service through a single annotation on the RGD. In GitOps mode, every deployment generates Kubernetes manifests and commits them to your Git repository instead of applying directly to the cluster. Your GitOps tool (ArgoCD, Flux, etc.) then syncs from Git as usual. Developers get the same simple form experience; the difference is where the output lands.
Three Deployment Modes. You Choose.
Enforce how each service gets deployed. Set it once per RGD. Developers follow the path you define.
Direct
Deploy straight to the cluster via the Kubernetes API. Best for development environments and rapid iteration.
GitOps
Generate manifests and commit to Git. Your GitOps tool (ArgoCD, Flux) syncs from there. Full audit trail.
Hybrid
Deploy to the cluster and commit to Git simultaneously. Cluster state and Git stay in sync from day one.
Modes are enforced per service via annotations. When only one mode is allowed, the UI auto-selects it and disables the selector so developers can't bypass your policy.
Key Capabilities
Self-service that fits your GitOps workflow
Git-First Workflow
Every GitOps deployment generates Kubernetes manifests and commits them to Git. Your repo is the source of truth, and your GitOps tool syncs from there.
Repository Integration
Connect to GitHub, GitLab, or Bitbucket. Knodex pushes directly to your preferred repository.
Per-Service Mode Enforcement
Set allowed deployment modes per RGD via a single annotation. When only one mode is allowed, the UI auto-selects it so developers can't bypass your policy.
Works with Any GitOps Tool
ArgoCD, Flux, or your custom solution. If it reads from Git, it works with Knodex.
Annotation-Driven Configuration
No separate config layer. Add knodex.io/deployment-modes to your RGD and specify which modes are allowed. Case-insensitive, whitespace-tolerant, backward-compatible.
Self-Service Preserved
Developers still get a simple deployment form regardless of mode. The only difference is where the manifests land: cluster, Git, or both.