Flux as a Managed Service
GitOps without an extra UI – built consistently on Kubernetes principles.
We set up Flux as GitOpsGitOps treats infrastructure like code – versioned, auditable, automatable. Learn more → continuous deployment for your Kubernetes clusters: several specialized controllers instead of one central application, fully API-first.
Flux: Managed Operations & Support
Lightweight, API-first continuous deployment for Kubernetes – a CNCF Graduated project, with no extra UI required.
- Setting up Sources, Kustomizations & HelmReleases
- Automatic sync on changes in the Git repository
- Optional: Weave GitOps UI for visualization
Why Flux?
Flux is a CNCF Graduated project that implements GitOps consistently through native Kubernetes custom resources:
- Several specialized controllers (source, Kustomize, Helm, notification) instead of one monolithic application
- Runs entirely as part of the Kubernetes API server – no separate UI required
- Supports Helm charts, Kustomize overlays, and plain manifests equally well
- Multi-tenancy and progressive delivery (e.g. via Flagger) are possible
What we take on for you
- Installation & configuration of the Flux controllers in your cluster
- Connection to your Git repository (Gitea, GitLab, or external)
- Definition of Sources, Kustomizations & HelmReleases
- Optional: setting up the Weave GitOps UI for visualization
- MonitoringMonitoring spots problems before they escalate – active oversight, not just reacting. Learn more → of reconciliation status & alerting
Who is this for?
- Teams that want to implement GitOps without an extra central UI
- Environments with a high degree of automation & custom-resource-based operations
- Progressive delivery scenarios (canary, blue/green) combined with Flagger
- Multi-tenant clusters with strict separation by namespace or team
Integration into your stack
- Managed Cluster & Managed Applications
- Git & CI/CD – Gitea, GitLab, or Woodpecker as the source
- Container Registries – Harbor or GitLab Container Registry as the image source
- Monitoring for reconciliation status & application health
Frequently asked questions
Flux or ArgoCD – what does RiKuWe recommend?
Both are mature GitOps tools. Flux is more lightweight, API-first, and usable without a separate UI. [ArgoCD](/services/kubernetes/argocd) comes with a clear web UI out of the box. We're happy to advise on the right choice for your environment.
Do we need a web UI for Flux?
Not necessarily. Flux works entirely through kubectl and custom resources. On request, we can additionally set up the Weave GitOps UI for visualization.
Does Flux support progressive delivery like canary deployments?
Yes, combined with Flagger. We set this up on request, for example for gradual rollouts with automatic rollback on failure.
Flux – professionally operated by RiKuWe
We take care of running your GitOps pipeline reliably – so deployments stay traceable and cluster state stays reproducible at any time.
Book an Appointment