Authentication
This provider requires authentication.- kubeconfig: Kubeconfig file content (required: False, sensitive: True)
- context: Kubernetes context to use (required: False, sensitive: False)
- namespace: Namespace where Flux CD is installed (required: False, sensitive: False)
- api_server: Kubernetes API server URL (required: False, sensitive: False)
- token: Kubernetes API token (required: False, sensitive: True)
- insecure: Skip TLS verification (required: False, sensitive: False)
- authenticated: User is Authorized (mandatory)
In workflows
This provider can be used in workflows. As “step” to query data, example:Topology
This provider pulls topology to Keep. It could be used in correlations and mapping, and as a context for alerts and incidents.Provider Methods
The provider exposes the following Provider Methods. They are available in the AI Assistant.- get_fluxcd_resources Get resources from Flux CD (, scopes: no additional scopes)
Overview
Flux CD is a GitOps tool for Kubernetes that provides continuous delivery through automated deployment, monitoring, and management of applications. This provider allows you to integrate Flux CD with Keep to get a single pane of glass for monitoring your GitOps deployments.Features
Topology
The Flux CD provider pulls topology data from the following Flux CD resources:- GitRepositories
- HelmRepositories
- HelmCharts
- OCI Repositories
- Buckets
- Kustomizations
- HelmReleases
- Source: GitRepositories, HelmRepositories, OCI Repositories, Buckets
- Deployment: Kustomizations, HelmReleases
Alerts
The Flux CD provider gets alerts from two sources:- Kubernetes events related to Flux CD controllers
- Status conditions of Flux CD resources (GitRepositories, Kustomizations, HelmReleases)
- Failed GitRepository operations
- Failed Kustomization operations
- Failed HelmRelease operations
- Non-ready resources
- Critical: Events with “failed”, “error”, “timeout”, “backoff”, or “crash” in the reason
- High: Other warning events
- Info: Normal events
Connecting with the Provider
The Flux CD provider supports multiple authentication methods:- Kubeconfig file content (recommended for external access)
- API server URL and token
- In-cluster configuration (when running inside a Kubernetes cluster)
- Default kubeconfig file (from ~/.kube/config)
Using Kubeconfig
Using API Server and Token
Note: Bothapi-server
andapi_server
formats are supported for backward compatibility.
Using In-Cluster Configuration
Comparison with ArgoCD Provider
Keep supports both Flux CD and ArgoCD for GitOps deployments. Here’s a comparison of the two providers:Feature | Flux CD | ArgoCD |
---|---|---|
Topology | ✅ | ✅ |
Alerts | ✅ | ✅ |
Resource Types | GitRepositories, HelmRepositories, Kustomizations, HelmReleases | Applications, Projects |
Authentication | Kubeconfig, API Server, In-Cluster | Username/Password, Token |
Deployment Model | Kubernetes Controllers | Server + Controllers |
UI Integration | No (CLI only) | Yes (Web UI) |