zarf-dev/zarf v0.14.0

on GitHub

Until we finish migrating from Repo1 to GitHub the release artifacts can be found HERE.

⚠️ Contains breaking changes. Please see release notes for details

Known issues

• Sometimes, usually after a zarf destroy, the .zarf-state.yaml and $HOME/.git-credentials files will get into a bad state, where the IP address / hostname is not present in the configuration, and zarf package deploy fails because it doesn't know where to push the docker images. This issue is resolved in v0.15.0 and can be mitigated on v0.14.0 by deleting .zarf-state.yaml and $HOME/.git-credentials (assuming there isn't other non-zarf stuff in it) after running zarf destroy. See #347 for more details.

What's Changed

• Add .tool-versions file (#191)
• Fix the Big Bang Core example to do GitOps correctly (#185)
• Loosen Terraform version restriction in E2E tests (#199)
• Doc updates (#198)
• PR #196 did a bunch of stuff:
  • ⚠️ BREAKING: localhost is no longer a valid option for cluster ingress when initializing a zarf cluster. Instead you have to use a 127.0.0.1 or some other local ip found via ifconfig.
  • Add the ability to choose from what should be valid hostnames or IP addresses when running zarf init due to the above breaking change
  • Stop depending on 127.0.0.1 local bindings for the registry & gitops service. Fixes #193
  • Resolve outstanding issues with image hostname swapping. Fixes #18, #44, and #194
  • Adds before and after script options when defining a zarf.yaml with an optional retry flag
  • Add symlink to ZarfFile for creating links to places files
  • Add template boolean to ZarfFile to allow injection of zarf variables into text files
  • Adds a new zarf tool command to print out config schema and commit the output to the repo (will need to make a git hook or something later on)
  • Changes zarf destroy command to run any script that starts with zarf-clean instead of only running the k3s-remove script
  • Add new ZarfState and .zarf-state.yaml for persisting host information from zarf init to zarf package deploy
  • Remove all hard-coded logic for k3s install, now uses only standard zarf component features like everything else
  • Upgrades k3s from v1.21.2 to v1.21.6
  • Adds optional regex filter for when performing RecursiveFileList()
  • Adds more description to the components in zarf.yaml
  • Renames type ZarfConfig to ZarfPackage in the config pkg
  • Handful of general code organizing changes (moving yaml related functions to the ...../utils/yaml.go, etc.)
  • Expose execCommand() with stdout control
  • Move traefik to standalone component and drop the internal k3s install of traefik
  • Use the airgap tarball of K3s instead of manually listing images