Aleksei Sviridkin 65a038caa4 docs(api): separate the healthCheckExprs failure modes ...

The field doc filed every mistake under one outcome, a HelmRelease
that hangs until its timeout. helm-controller treats them differently.
An expression that does not parse is rejected before any Helm action
and stalls the release at once, with a named reason. One that parses
but errors on the object keeps the wait polling with the CEL error
attached, and a current expression that evaluates cleanly but never
turns true runs the wait out with no error at all. A read of status
errors until the CR's controller writes one, even inside has(), but
the wait survives it. A wrong group or kind silently falls back to
the built-in readiness rules, and a CR whose CRD is missing fails the
Helm action before the wait starts.

The text ships in the CRDs and is what kubectl explain shows, so a
reader who cannot check it against the controller source was sent
to the wrong place for the parse error and the missing CRD.

Assisted-by: LLM
Signed-off-by: Aleksei Sviridkin <f@lex.la>

2026-09-23 00:05:35 +03:00

..

manifests

docs(api): separate the healthCheckExprs failure modes

2026-09-23 00:05:35 +03:00

install_test.go

test(crdinstall): assert no-delete label survives Install + merge

2026-05-26 15:12:52 +05:00

install.go

feat(platform): add deletion-protection guardrail via ValidatingAdmissionPolicy

2026-05-26 14:18:22 +05:00

manifests.embed.go

fix(crdinstall): use filepath for OS paths, restrict permissions, add tests

2026-02-18 00:49:56 +03:00