Nearle/kubernetes
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Exclude nearle-ariane.yaml from Flux sync - crash-loops on first deploy

Browse Source 
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 <noreply@anthropic.com>
This commit is contained in:
Suriya
2026-07-20 10:58:52 +05:30
parent ffef003a2b
commit f883540272
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
manifests/nearle/kustomization.yaml
View File

@@ -12,6 +12,10 @@ resources:
- jupiter-cors-proxy.yaml - jupiter-cors-proxy.yaml
- nearle-atlantis.yaml - nearle-atlantis.yaml
- nearle-titan.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-gateway.yaml
- nearle-reference-grant.yaml - nearle-reference-grant.yaml