Skip to main content

Understand The Basics

Before you can effectively use Zarf, it is useful to have an understanding of the technology Zarf is built on and around. The sections below provide some helpful links to start building up this foundation as well as a glossary of the terms used in this project.

Technologies

Kubernetes

AirGap Basics

GitOps Basics

CLI Basics

Terms Used

  • Declarative: A user states (via configuration file) which resources are needed and Zarf locates & packages them. A user does not have to know how to download, collect, roll, and unroll dependencies for transport, they only have to know what they need.
  • Package: A well-defined, tool-generated, versioned, and compressed collection of software intended for movement (and later use) across a network / administrative boundary.
  • Remote systems: Systems that are organized such that development & maintenance actions occur primarily in locations physically & logically separate from where operations occur.
  • Constrained systems: Systems with explicit resource / administrative / capability limitations.
  • Independent systems: Systems are organized such that continued operation is possible even when disconnected (temporarily or otherwise) from external systems dependencies.
  • Air-gapped systems: Systems are designed to operate while physically disconnected from "unsecured" networks like the internet. More on that here.