From f88354027219e4ef82b42c0100f442cc1251cab3 Mon Sep 17 00:00:00 2001 From: Suriya Date: Mon, 20 Jul 2026 10:58:52 +0530 Subject: [PATCH] Exclude nearle-ariane.yaml from Flux sync - crash-loops on first deploy ariane was never actually running on the cluster before this rollout (not in any prior pod listing); Flux deploying it for the first time exposed it's broken, unrelated to the GitOps migration itself. Pulling it out of scope so it stops blocking the nearle Kustomization's health check for the services that do work (fiesta, jupiter, atlantis, titan). Co-Authored-By: Claude Sonnet 5 --- manifests/nearle/kustomization.yaml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/manifests/nearle/kustomization.yaml b/manifests/nearle/kustomization.yaml index c25213e..fc97cd4 100644 --- a/manifests/nearle/kustomization.yaml +++ b/manifests/nearle/kustomization.yaml @@ -12,6 +12,10 @@ resources: - jupiter-cors-proxy.yaml - nearle-atlantis.yaml - nearle-titan.yaml - - nearle-ariane.yaml + # nearle-ariane.yaml intentionally excluded - it was never actually + # running on the cluster before Flux tried to deploy it for the first + # time, and it crash-loops. Not a GitOps regression, a pre-existing + # dormant/broken manifest. Revisit separately from the alaska/nearle + # rollout. - nearle-gateway.yaml - nearle-reference-grant.yaml