# platform/kyverno — in-cluster ENFORCING bundle (Kyverno install + policies shared verbatim with
# the CI L0 gate; ADR-0011, docs/07 admission enforcement).
#
# Resources are listed with DOWNWARD paths only (no `../`) so this builds under default kustomize
# load restrictions. The admission/kustomization.yaml authored by WS-TEST uses `../policies` refs and
# is kept as reference; THIS file is the buildable render root.
#
# NOTE: not yet wired into platform/kustomization.yaml — admission enforcement is Phase 2 (T-2.7),
# which needs a cluster. Scaffolding is present and buildable now.
#
# CI-only artifacts (tests/, servicedefinition/ payloads, scripts/run-l0.sh) are intentionally NOT
# rendered into the cluster — they run in CI (.gitea/ + ci/).
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
namespace: kyverno
resources:
  - admission/namespace.yaml
  - admission/helmrelease.yaml
  # NOTE: the ClusterPolicies (policies/*.yaml) + admission/secret-provenance.yaml are kyverno.io CRs
  # → applied by the platform-config Kustomization (dependsOn platform) so the Kyverno CRDs exist
  # first. Files STAY here so the CI L0 gate (`kyverno test platform/kyverno/`) still discovers them.