Flux Health Checks and Readiness
What you'll learn: How to configure Flux to verify that deployed resources are actually healthy and ready before marking a deployment successful.
Why Health Checks Matter in GitOps
When Flux applies your manifests to Kubernetes, it doesn't just fire-and-forget. You need confirmation that your Deployment created healthy Pods, your Service got endpoints, or your Ingress controller picked up the new route. Without health checks, Flux might report "success" while your application is actually crash-looping.
Think of it like ordering furniture online: the delivery isn't complete when the box arrives at your door—it's complete when you've unpacked it, assembled it, and verified it works as expected.
Configuring Health Assessment
Flux's Kustomization resource includes a healthChecks field where you specify which resources to monitor:
apiVersion: kustomize.toolkit.fluxcd.io/v1
kind: Kustomization
metadata:
name: my-app
namespace: flux-system
spec:
sourceRef:
kind: GitRepository
name: my-repo
path: ./apps/production
prune: true
interval: 10m
healthChecks:
- apiVersion: apps/v1
kind: Deployment
name: backend
namespace: default
This tells Flux: "Don't consider this reconciliation successful until the backend Deployment is healthy (all replicas ready)."
How Flux Determines Readiness
Flux evaluates health based on Kubernetes-native status conditions. For Deployments, it checks that desired replicas match available replicas. For Services with type LoadBalancer, it waits for an external IP. You define what to check; Flux handles the waiting.
Key Takeaway: Flux health checks ensure your GitOps reconciliation waits for actual application readiness, not just manifest application, preventing false positives and enabling safer automated deployments.