Skip to content

Verification & Architecture

Health checks, diagnostic commands, and system design overview.

Verification Commands

Check Flux health:

flux check

List Flux resources:

flux get sources git -n flux-system
flux get kustomizations -n flux-system

Reconcile app manifests:

flux reconcile source git flux-system -n flux-system
flux reconcile kustomization apps -n flux-system
kubectl -n flux-system describe kustomization apps

Validate app deployment status:

kubectl get ns platform-api platform-web
kubectl -n platform-api get deploy,pods,svc
kubectl -n platform-web get deploy,pods,svc

Functional smoke tests:

kubectl port-forward --address 0.0.0.0 -n platform-api svc/api 8000:8000
curl http://127.0.0.1:8000/health

kubectl port-forward --address 0.0.0.0 -n platform-web svc/web 4321:4321
curl http://127.0.0.1:4321/

View logs:

flux logs -n flux-system --follow

Check GitRepository status:

kubectl get gitrepository -n flux-system -o yaml

Architecture

Main Branch (GitHub)
       ↓
  GitRepository (watches main, 1m interval)
       ↓
git clone → Kustomization (applies gitops/clusters/dev)
       ↓
Flux Controllers (reconcile)
       ↓
gitops-dev Cluster

Changes pushed to main branch are automatically applied to the cluster within ~1 minute.

Why This Approach Works

  1. Unprotected bootstrap: Flux bootstrap succeeds because it commits to feat-fluxcd-dev
  2. Config switch: Single commit changes where Flux watches (from feat-fluxcd-dev to main)
  3. Protected main: Main branch protection rules enforce code review (Flux doesn't bypass this)
  4. Transparent workflow: Everything visible in Git history for audit and rollback

This workflow enables GitOps automation while respecting branch protection policies required for production safety.