Zarf 1.0 released with v1beta1 schema and improved airgap delivery security
Zarf 1.0 introduces a redesigned package schema and a transition from variables to structured values to improve secure software delivery in disconnected environments.
Summary
Defense Unicorns has announced the 1.0 release of Zarf, a tool designed to facilitate the declarative creation and distribution of software into air-gapped and constrained environments. This major update focuses on enhancing security, stability, and long-term project sustainability for users operating in disconnected settings.
The release introduces the v1beta1 Zarf package schema, which replaces older, deprecated features with a more intuitive system. Key improvements include stronger package signing and verification workflows, alongside a shift from using unstructured variables to a structured 'values' system using standard Go templating.
Technical changes in Zarf 1.0
- Schema Redesign: The introduction of the v1beta1 package schema provides a foundation for long-term compatibility and includes new features for component publishing for imports.
- Configuration Management: The system transitions from using ###ZARF_VAR_*### variables to a structured 'values' approach, supporting nested data and standard Go templating for better readability.
- Security Enhancements: The 1.0 release implements more robust workflows for package signing and verification to ensure provenance in disconnected environments.
- Migration Tooling: To assist with the transition to the new schema and value system, the release includes a dedicated migration guide and automated tooling for existing packages.
Why it matters
For DevOps engineers and system administrators managing Kubernetes clusters in high-security or disconnected environments, Zarf 1.0 provides a more predictable and secure method for deploying software without internet access. The move toward structured Go templating and improved signing workflows reduces the risk of configuration errors and supply chain vulnerabilities during airgap transfers.
Original reference: openssf.org →