organize deployment configuration
Kube-bench CIS scan / Scan ephemeral K3s cluster (push) Successful in 1m6s

This commit is contained in:
2026-08-15 13:17:46 -04:00
parent 12f3276465
commit fc53e16dd4
18 changed files with 26 additions and 13 deletions
+16
View File
@@ -5,6 +5,22 @@ fast reproducible demo, optional Flatcar plus Terraform and Ansible for a cloud
K3s host, Cilium eBPF networking, CIS Benchmark checks in CI, Kyverno
admission policies, and Falco runtime detection.
## Repository layout
Deployment and GitOps configuration is grouped under `deployments/`:
```text
deployments/
├── argocd/ # app-of-apps and child Application definitions
├── cilium/ # Cilium Helm values for the optional kube-proxy-free path
└── falco/ # Falco Operator values and custom resource definitions
```
The platform payloads remain separate from their deployment definitions. Kyverno
policies live under `policies/`, runtime demonstration workloads live under
`test-workloads/`, and cluster provisioning code remains under `terraform/`,
`ansible/`, and `local-quickstart/`.
## Phase 1: provision a local cluster
The primary quick-start path requires Docker, k3d, and kubectl: