The HelmRelease is stuck reconciling and never rendered a Deployment — no pods at all. fleet/www prod on the same cluster is healthy (InstallSucceeded, 1/1 running), so this is app/release-specific, not a cluster-wide outage.
Notes toward root cause
"Deployment not found" + long-running Progressing means the install is blocked before the Deployment is created — typical causes: a Helm dependency/wait, a values/template error in the www chart, or an admission (kyverno) block during render. Needs the flux helm-controller / source-controller logs on the EKS cluster to pin down (app has 0 pods, so tail_logs returns nothing).
Distinct from L3: on EKS, image pulls use the node ECR role, not an ecr-cred secret, so this is not the same failure mode.
The EKS TLS path is also currently half-landed (see PR #212 C3/C4) — if www's chart waits on a cert/Ingress readiness, that could stall the release; worth checking whether the two are related.
Fix (lands on the EKS cluster, tracked here)
Pull helm-controller/source-controller logs for open-platform--www--prod on git.aws.benjivers.com and identify the blocking resource.
Reconcile or roll back the HelmRelease; if it's a chart/values defect, fix in the open-platform/www app repo on that host.
Feed anything generalizable (e.g. install-retry / remediation on HelmRelease) back as a real plat/mitosis source hardening if warranted.
Found during the AWS audit (PR #212, finding L1). This is a live issue on the
git.aws.benjivers.comEKS cluster.Symptom
open-platform/wwwprod:The HelmRelease is stuck reconciling and never rendered a Deployment — no pods at all.
fleet/wwwprod on the same cluster is healthy (InstallSucceeded, 1/1 running), so this is app/release-specific, not a cluster-wide outage.Notes toward root cause
Progressingmeans the install is blocked before the Deployment is created — typical causes: a Helm dependency/wait, a values/template error in thewwwchart, or an admission (kyverno) block during render. Needs the fluxhelm-controller/source-controllerlogs on the EKS cluster to pin down (app has 0 pods, sotail_logsreturns nothing).ecr-credsecret, so this is not the same failure mode.www's chart waits on a cert/Ingress readiness, that could stall the release; worth checking whether the two are related.Fix (lands on the EKS cluster, tracked here)
helm-controller/source-controllerlogs foropen-platform--www--prodongit.aws.benjivers.comand identify the blocking resource.open-platform/wwwapp repo on that host.remediationon HelmRelease) back as a real plat/mitosis source hardening if warranted.Ref: audit PR #212 →
docs/ops/aws-audit-2026-08-25.md(L1).