fix(kyverno): Remove kyverno from setup
It's the 3rd update of kyverno and each time, things break in minor version. This is no modi operandi for this setup. Things are supposed to be stable and solid to work with. Kyverno is too unstable for this use-case. This time the installation of the pods failed due to wrong deployment names. This is nothing we change or adjust. Further the removal doesn't have any major impact on the platform, since network policies are already deployed via gitops from the `shared/` directory. BREAKING CHANGE: Removing kyverno and related CRDs/APIs.
Showing
- bootstrap/kyverno/kustomization.yaml 0 additions, 7 deletionsbootstrap/kyverno/kustomization.yaml
- bootstrap/kyverno/namespace.yaml 0 additions, 7 deletionsbootstrap/kyverno/namespace.yaml
- bootstrap/kyverno/release.yaml 0 additions, 27 deletionsbootstrap/kyverno/release.yaml
- bootstrap/kyverno/repository.yaml 0 additions, 8 deletionsbootstrap/kyverno/repository.yaml
- infrastructure/kyverno/allow-from-same-namespace-network-policies.yaml 0 additions, 32 deletions...e/kyverno/allow-from-same-namespace-network-policies.yaml
- infrastructure/kyverno/deny-network-policies.yaml 0 additions, 20 deletionsinfrastructure/kyverno/deny-network-policies.yaml
- infrastructure/kyverno/deny-system-namespaces.yaml 0 additions, 21 deletionsinfrastructure/kyverno/deny-system-namespaces.yaml
- infrastructure/kyverno/kustomization.yaml 0 additions, 9 deletionsinfrastructure/kyverno/kustomization.yaml
- infrastructure/kyverno/quotas.yaml 0 additions, 68 deletionsinfrastructure/kyverno/quotas.yaml
- infrastructure/kyverno/release.yaml 0 additions, 18 deletionsinfrastructure/kyverno/release.yaml
bootstrap/kyverno/kustomization.yaml
deleted
100644 → 0
bootstrap/kyverno/namespace.yaml
deleted
100644 → 0
bootstrap/kyverno/release.yaml
deleted
100644 → 0
bootstrap/kyverno/repository.yaml
deleted
100644 → 0
infrastructure/kyverno/quotas.yaml
deleted
100644 → 0
infrastructure/kyverno/release.yaml
deleted
100644 → 0
Please register or sign in to comment