fix argo health check

2026-08-31 06:43:23 +05:30
parent 69c2807fd7
commit 775c2ef79e
4 changed files with 149 additions and 0 deletions
@@ -76,6 +76,18 @@ argo-cd:
      url: "https://argocd.192.168.1.7.nip.io"
      timeout.reconciliation: 3m
      timeout.reconciliation.jitter: 60s
+      # ArgoCD's built-in Ingress health check waits for
+      # status.loadBalancer.ingress to be populated — that only happens
+      # behind a Service type=LoadBalancer. Contour here is exposed via
+      # hostPort (MetalLB is installed but not load-bearing, see
+      # claude.md), so nothing ever writes that status field and every
+      # Ingress sits "Progressing" forever even though it's actually
+      # serving traffic fine. Override: an Ingress existing is enough.
+      resource.customizations.health.networking.k8s.io_Ingress: |
+        hs = {}
+        hs.status = "Healthy"
+        hs.message = "Ingress considered healthy on sight — this cluster's Contour has no LoadBalancer status to wait on (hostPort, not MetalLB)."
+        return hs
    # No custom RBAC policy: single-user homelab, the initial admin secret
    # (kubectl -n argocd get secret argocd-initial-admin-secret) is enough.
    # The fleet's role:admins / role:backend / GitHub-team policy.csv and