How chenlevin89/sandbox works
Project type and purpose
• This repository is a Helm‐based Kubernetes packaging project (“sandbox”) that provides multiple Helm charts and subcharts to deploy Telepresence into a cluster.
• There are three “charts” in play:
– A root-level chart (Chart.yaml, values.yaml, templates/)
– A telepresence subchart (folder telepresence/)
– A second variant subchart (folder telepresence_new/)
• Each of the telepresence folders is a full Helm chart (Chart.yaml + values.yaml + templates) packaging Telepresence components—agent, traffic‐manager, webhook injector, RBAC rules, certificates, etc.
File structure
• Top-level:
– .helmignore, Chart.yaml, values.yaml, templates/ → this is the parent chart scaffold
– apps/app-1.yml → an example or test manifest not managed by Helm
– telepresence-2.17.1.tgz → a packaged chart archive (dependency)
• Subcharts (telepresence/ and telepresence_new/):
– Chart.yaml + values.yaml → metadata + default configuration
– templates/ → Kubernetes resources (Deployments, Services, ConfigMaps, RBAC, Webhook, Issuer, etc.)
• The duplication between telepresence/ and telepresence_new/ suggests either A/B testing or two versions of the Telepresence chart.
README
• README.md simply says “# sandbox,” so we infer nothing extra. All architectural details come from the file tree and knowledge of Telepresence.
Capturing essential architectural elements
• Don’t just list files—group them by function (packages vs templates vs runtime).
• How the Helm chart hierarchy maps to real Kubernetes resources.
• Injection pattern (webhook → sidecar) that is core to Telepresence.
• Two subchart variants side by side to highlight versioning or A/B use.
• Values.yaml as the customization/control point for each chart.