Files
Aleksei Sviridkin d558920c84 docs(cozystack-basics): distinguish the two VAP capability-gate cases
The dependsOn comment warned that a capability gate renders the policy out at
first install and never re-adds it, which read as contradicting the
.Capabilities.APIVersions.Has guard the policy templates now carry. They do not
conflict: the warning is about gating on the matched types' CRDs, which may not
exist yet at first install, while the template guard names the ValidatingAdmission
Policy API itself — GA on every supported cluster, so always present. Spell out
that a maybe-absent matched-type CRD needs dependsOn ordering while an
always-present core API can be gated in the template.

Signed-off-by: Aleksei Sviridkin <f@lex.la>
2026-07-21 17:18:14 +03:00
..