Zarf Air Gap

Veckl supports disconnected deployments with Zarf. The package includes the backend image, frontend image, and Kubernetes manifests.

Connected Build Environment

In a connected environment, build the images:

make container-build
make container-build-frontend

Create the Zarf package:

zarf package create --confirm

This produces a package file named like:

zarf-package-veckl-*.tar.zst

Move that package into the disconnected environment using your approved transfer process.

Disconnected Target Environment

Deploy the package:

zarf package deploy zarf-package-veckl-*.tar.zst --confirm

Then open the configured Ingress host or port-forward the frontend service:

kubectl port-forward -n veckl service/veckl-frontend 3000:3000

npm Registry Mirrors

If you build the frontend image in a restricted network, point npm at an internal registry mirror:

make container-build-frontend NPM_REGISTRY_URL=https://mirror.example.com/npm/

Go dependencies are vendored in the repository. Frontend dependencies are installed during the frontend image build.

Catalog Data in Air-Gapped Environments

Use Air-Gapped Export from a connected Veckl environment to produce a catalog file. Import that file in the disconnected environment from Admin > Catalog.

This avoids needing the disconnected backend to reach the public NIST OSCAL source.