Envoy Gateway's per-route default timeout (15s, unset anywhere in this
cluster) was cutting the connection to argocd-server mid-Sync, surfacing
as 'Gateway Timeout' in the UI — confirmed even a single-resource sync
hit exactly ~15.0s every attempt, ruling out chart size/congestion.
BackendTrafficPolicy on the argocd HTTPRoute raises requestTimeout to 120s.
nfs-subdir-external-provisioner chart v4.0.18 has no extraObjects
values key - it was silently ignored, so nfs-retain never actually
existed. Only nfs-delete (native storageClass.* key) is real.
Updated README expected output to match.
ArgoCD only builds a helm-pull command for oci:// sources when the repo is
registered with enableOCI: true; otherwise it falls back to classic --repo
handling, which errors on an oci:// URL. Registered via configs.repositories
in argocd's own values.yaml (Git-managed), Application source updated to
the bare host/path form ArgoCD expects for OCI repos.
Drop .env/envsubst/bake-hash-into-values.yaml flow entirely. Chart's
configs.secret block is removed for good, so the rendered manifest
never declares admin.password/admin.passwordMtime. Password hash is
set once directly on the live argocd-secret via kubectl patch, and
survives every self-heal sync since ArgoCD never owns those fields.
- remove server.httproute from argocd values.yaml: helm install failed
since Gateway API CRDs (installed by envoy-gateway, wave 2) don't
exist yet; HTTPRoute is already applied manually in Phase 6
- add bootstrap-app.yaml as the Git-committed root/seed Application,
replacing ad-hoc UI creation (GitOps anti-pattern: apps not stored
in Git can't be recreated)
duynguyen