DEMO LABMANIFESTS
The YAML the demo actually runs.
Every cluster-side mutation the live demo performs is a file in this directory. No hidden Ansible, no inline --set gymnastics that the terminal pane can't show. Read the YAML; don't trust the narration.
| File | Applied at | What it does |
|---|---|---|
payments-api-deployment.yaml |
Step 1 | The stand-in workload (busybox httpd pretending to be a payments API, namespace demo-app). Not a real payments API. |
cloudtaser-helm-values.yaml |
Step 4 | Helm values: beacon address + fingerprint verification ON. Operator + webhook + eBPF agent + wrapper. |
postgres-annotations.yaml |
Step 5 | The four cloudtaser.io/* annotations that opt this Deployment into CloudTaser injection. One YAML change, everything else transparent. |
README.md |
— | Per-field commentary + step-by-step mapping of what runs when. |
Not in this directory
- The cloudtaser-operator / wrapper / eBPF chart manifests live in cloudtaser/cloudtaser-helm.
- The cloudtaser-beacon + cloudtaser-onprem (bridge) binaries are installed on the EU VMs by Ansible in cloudtaser-demo/demo-lab/ansible.
- The orchestrator + probe whitelist + step whitelist live in cloudtaser-demo/demo-lab.