The suites asserted the toServices rule that produced the cluster-wide 443
deny, so they pinned the defect: every rendered-YAML assertion passed on the
broken policy, and removing the rule would have read as the regression.
Replace those cases with the invariant that was actually missing -- one deny
rule per spec, and its destination must be a selector Cilium can resolve
(toEndpoints present, toServices absent, spec count fixed). Verified by
mutation: reintroducing the toServices rule fails these assertions in both
packages.
Not used: matchRegexRaw / notMatchRegexRaw. helm-unittest 1.0.3 silently
ignores both -- a notMatchRegexRaw against a pattern guaranteed to be present
still reports pass -- so a document-wide regex guard would have asserted
nothing.
packages/system/kubeovn-webhook had no Makefile test target, and
hack/helm-unit-tests.sh discovers suites by probing `make -n test` per package
and skips any package without one. All three of its suites -- including the
port agreement guard, whose whole purpose is to catch a drift that fails open
-- had therefore never run in CI. Add the target; the sweep now reports
"Running tests in packages/system/kubeovn-webhook".
Assisted-By: Claude <noreply@anthropic.com>
Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>