How zarf-dev/zarf works
Main Components
a. Core Components:
• CLI Interface (entry point)
• Package Manager
• Cluster Manager
• Registry Services
• Git Services (Gitea)
• Injection System
• SBOM Generator
• Authentication/Security Layer
b. External Integrations:
• Kubernetes Clusters
• OCI Registries
• Git Repositories
• Container Images
• Helm Charts
User Interface Layer
• CLI Commands (zarf init, package, connect, etc.)
• Interactive Prompts
• Configuration Management
Core Processing Layer
• Package Management System
• Component Processor
• Variable Template Engine
• Action Runner
• Image Transformer
Integration Layer
• Kubernetes Client
• Registry Client
• Git Client
• Helm Client
• SBOM Tools
Infrastructure Layer
• Local Storage
• Network Services
• Security Services
• Caching System
Key Relationships to Highlight
• Bidirectional flow between CLI and Package Manager
• How the Mutating Webhook interacts with Kubernetes
• Demonstrate the transformation pipeline for container images
• Relationship between packages and their components
• Flow of SBOMs and security scanning
Important Details
• Package Creation Flow
• Deployment Pipeline
• Air Gap Boundary
• Security Checkpoints
• Component Lifecycle
• Resource Transformation Points
Specific Implementation Notes
• Zero-dependency nature of the CLI
• Composable package system
• Where variable templating occurs
• Points where SBOM generation happens
• Where cosign signature verification takes place