Flux Integration
GitOps reconciliation events and Kustomization health from Flux controllers. Monitor sync failures, HelmRelease status, and correlate every GitOps change with application performance.
How It Works
Deploy the TigerOps Flux Monitor
Install the TigerOps Flux monitor via Helm or Flux itself. It watches Kustomization, HelmRelease, GitRepository, and HelmRepository objects and exports their status as Prometheus metrics.
Configure Remote Write
Point the monitor to your TigerOps remote-write endpoint using a Kubernetes Secret for your API key. Reconciliation duration, ready conditions, and failure counts begin flowing immediately.
Enable Notification Controller Events
Configure a Flux Alert and Provider targeting TigerOps to receive real-time GitOps events — sync started, reconciliation failed, health check timeout — without polling.
Correlate Reconciliations with App Metrics
TigerOps overlays every successful Flux reconciliation as a change event on your APM dashboards, enabling instant identification of which GitOps commit introduced a regression.
What You Get Out of the Box
Kustomization Reconciliation Health
Track ready status, last applied revision, reconciliation duration, and failure reasons for every Kustomization in your cluster. TigerOps alerts on stalled or failing reconciliations before they impact workloads.
HelmRelease Status Monitoring
Monitor HelmRelease ready conditions, chart version history, upgrade failure counts, and rollback events. Get notified when a HelmRelease enters a failed or remediation state with full status context.
GitRepository Sync Tracking
Track GitRepository fetch intervals, last observed revision, and artifact availability. TigerOps alerts when a source fails to pull for longer than your configured threshold.
Drift Detection Alerting
When Flux detects drift between the cluster state and the Git source and triggers a reconciliation, TigerOps records the drift event and correlates it with any metric anomalies that preceded it.
Multi-Tenant Namespace Visibility
TigerOps aggregates Flux controller metrics across all namespaces and tenants, providing a fleet-wide view of GitOps health with per-namespace drill-down for multi-team clusters.
Flux Controller Resource Metrics
Monitor source-controller, kustomize-controller, helm-controller, and notification-controller memory, CPU, and work queue depth to ensure Flux controllers are healthy and keeping up with workloads.
Flux Alert & Provider for TigerOps
Create a Flux Provider and Alert to forward reconciliation events to TigerOps in real time.
# Flux notification-controller resources for TigerOps
# Apply with: kubectl apply -f flux-tigerops-alert.yaml
---
apiVersion: v1
kind: Secret
metadata:
name: tigerops-webhook-secret
namespace: flux-system
stringData:
address: https://ingest.atatus.net/api/v1/flux/events
token: ${TIGEROPS_API_KEY}
---
apiVersion: notification.toolkit.fluxcd.io/v1beta3
kind: Provider
metadata:
name: tigerops
namespace: flux-system
spec:
type: generic-hmac
secretRef:
name: tigerops-webhook-secret
---
apiVersion: notification.toolkit.fluxcd.io/v1beta3
kind: Alert
metadata:
name: tigerops-all-events
namespace: flux-system
spec:
providerRef:
name: tigerops
# Forward all severity levels for full reconciliation visibility
eventSeverity: info
eventSources:
- kind: Kustomization
name: "*"
- kind: HelmRelease
name: "*"
- kind: GitRepository
name: "*"
- kind: HelmRepository
name: "*"
# Annotate events with cluster name for multi-cluster setups
summary: "cluster=production"Common Questions
Which Flux versions does TigerOps support?
TigerOps supports Flux v2 (the GitOps Toolkit) including all controller versions currently maintained by the Flux project. The monitor uses the Flux controller metrics endpoints which are stable across v2 minor versions.
How does TigerOps receive Flux events without polling?
Flux has a built-in notification-controller with Alert and Provider resources. TigerOps provides a generic webhook Provider type — you create a Provider pointing to your TigerOps endpoint and Alerts scoped to the events you want, and Flux pushes events as they occur.
Can TigerOps show which Git commit caused a reconciliation failure?
Yes. Flux includes the source revision (Git commit SHA or tag) in every reconciliation event. TigerOps stores this with the event and links to your Git provider, so you can click through to the exact commit that caused a failure.
Does TigerOps support monitoring Flux in multi-cluster environments?
Yes. Deploy the TigerOps Flux monitor to each cluster and tag the remote-write configuration with a cluster label. TigerOps aggregates across clusters in dashboards while preserving per-cluster drill-down.
How are HelmRelease rollbacks handled in TigerOps?
When Flux triggers a HelmRelease rollback, TigerOps records the rollback event with the failed release version, the target rollback version, and the failure reason. This appears as a change event on dashboards so you can correlate with metric recovery after the rollback.
Full Visibility Into Your GitOps Reconciliation Loop
Kustomization health, HelmRelease status, and change-to-incident correlation. Deploy in 5 minutes.