Declare Argo CD Core v3.5.3 on railiance01 and its resource bounds
Some checks failed
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Has been cancelled

Pinned core-install.yaml (sha256 1a87025d...c448) with a kustomize
resources patch for the four workloads. The unpatched pin diffs clean
against live; the resources patch is declared only, and its apply waits
on the founder in RAIL-EN-WP-0002-T02. SCOPE.md no longer says ArgoCD is
absent from railiance01.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 63291@bnt-lap001
Assistant-Session: 8bd77868-ca68-4f49-bb1e-d539ecc0d703
This commit is contained in:
tegwick 2026-09-21 18:41:24 +02:00
parent f91a5298cb
commit 70295b6b2b
8 changed files with 284 additions and 13 deletions

View file

@ -10,4 +10,18 @@ check: ## Verify workflow templates remain private and deployment-free
test: ## Run enablement regression tests
python3 -m unittest discover -s tests -v
.PHONY: help check test
ARGOCD_DIR := deploy/argocd/railiance01
include $(ARGOCD_DIR)/PIN
argocd-fetch: ## Fetch the pinned Argo CD core manifest and verify its sha256
mkdir -p $(ARGOCD_DIR)/upstream
curl -fsSL -o $(ARGOCD_DIR)/upstream/core-install.yaml $(ARGOCD_MANIFEST_URL)
echo "$(ARGOCD_MANIFEST_SHA256) $(ARGOCD_DIR)/upstream/core-install.yaml" | sha256sum -c -
argocd-render: argocd-fetch ## Render the declared Argo CD state (no cluster contact)
kubectl kustomize $(ARGOCD_DIR)
argocd-diff: argocd-fetch ## Read-only server-side diff of declared Argo CD state against railiance01
kubectl kustomize $(ARGOCD_DIR) | ssh railiance01 'kubectl diff --server-side -n argocd -f -'
.PHONY: help check test argocd-fetch argocd-render argocd-diff