Flux Kustomize Health Quick Fix - Health Check Configuration

Flux Kustomization health checks verify that applied resources are healthy. Missing or incorrect health checks mark deployments as Ready before they're actually functional. This guide covers the fix.

Quick Fix

Wrong

spec:
  healthChecks:
  - apiVersion: apps/v1
    kind: Deployment
    name: my-app
    namespace: apps

The issue: health check targets a specific Deployment but does not wait for it to be ready. Missing timeout means Flux may wait indefinitely.

Right

spec:
  healthChecks:
  - apiVersion: apps/v1
    kind: Deployment
    name: my-app
    namespace: apps
  - apiVersion: v1
    kind: Service
    name: my-app
    namespace: apps
  timeout: 5m

# Expected output after applying the fix
# Health checks verify Deployment my-app is Ready
# Service my-app exists and has endpoints
# Timeout: 5 minutes for health check completion
# Kustomization ready only after all health checks pass

Prevention

• Add health checks for Deployments, Services, and other critical resources
• Set timeout to limit health check waiting period
• Use health checks for custom resources with failure: true conditions
• Monitor health check status with flux get kustomizations -o wide
• Use kubectl describe kustomization for detailed health status

DodaTech Tools

Doda Browser's health check dashboard shows resource readiness and health status. DodaZIP archives health check configurations for compliance. Durga Antivirus Pro monitors health check failures.

FAQ