Files
home-network-k3s-impl/platform/kustomization.yaml
T
jakman85andClaude Opus 4.8 587201317b PM integration: wire platform/kyverno into the platform render
Add platform/kyverno/kustomization.yaml (renders the admission enforcing bundle)
and enable the kyverno component in platform/kustomization.yaml (first, so
admission policies precede other components). kustomize build verified.

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
2026-08-16 00:09:15 -05:00

26 lines
911 B
YAML

---
# Top-level platform kustomization — the entrypoint the Flux `platform` Kustomization renders
# (clusters/base/platform.yaml, path: ./platform).
#
# Phase 0 scaffolding: lists every platform component EXCEPT kyverno (owned by the policy engineer,
# WS-TEST — see platform/README.md).
#
# ⚠️ INTEGRATION TODO(PM): once platform/kyverno/ is authored by the policy engineer, uncomment the
# `- kyverno` line below. Keep it FIRST so admission policies are present before other components
# reconcile. This workstream must NOT create files under platform/kyverno/.
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
resources:
- kyverno # PM: enabled — admission enforcer first so policies precede other components
- cilium
- longhorn
- cert-manager
- externaldns
- gateway
- monitoring
- velero
- kubevirt
- image-automation
- keycloak
- oauth2-proxy