jakman85andClaude Opus 4.8
428361f8c5
The prior integration commit enabled kyverno in the platform render, but (a) the admission bundle used ../policies refs that fail default kustomize load restrictions, and (b) admission enforcement is Phase 2 (T-2.7), not Phase 0. Fix: platform/kyverno/kustomization.yaml now lists resources with downward paths (builds standalone); platform/kustomization.yaml re-defers kyverno with a Phase-2 note. All Phase-0 gates green: kustomize (platform, platform/kyverno, dev), schema validation, conformance scaffold. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
25 lines
1.1 KiB
YAML
25 lines
1.1 KiB
YAML
# 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
|
|
- policies/require-default-deny-baseline.yaml
|
|
- policies/validate-default-deny-shape.yaml
|
|
- policies/restrict-host-namespaces.yaml
|
|
- policies/require-egress-class-label.yaml
|
|
- policies/require-auth-mode-label.yaml
|
|
- admission/secret-provenance.yaml
|