v0.12.0

What's Changed

zarf init Now always installs the private Docker registry.

⚠️ Contains breaking changes

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

⚠️ BREAKING: New schema for zarf.yaml config

The schema for the zarf.yaml config file has changed. It has been simplified now that the docker registry is always present, there's no need for making a distinction between local and remote images. They are now all what used to be called "remote".

New:

kind: ZarfPackageConfig
metadata:
  name: foo
  description: "Foo example"

components:
  - name: baseline
    required: true
    manifests: manifests
    repos:
      - https://repo1.dso.mil/platform-one/big-bang/[email protected]
    images:
      - registry1.dso.mil/ironbank/big-bang/base:8.4

  - name: optional-feature
    required: false
    default: true
    files:
      - source: https://example.com/foo
        shasum: 52299bd5a2df28b6a6ff9926e09abd0fa5e6c1094f5bb75b036a0452cfc00dfa
        target: "/usr/local/bin/foo"
        executable: true

Previous:

kind: ZarfPackageConfig
metadata:
  name: foo
  description: "Foo example"

components:
  - name: baseline
    required: true
    manifests: manifests
    images:
      - registry1.dso.mil/ironbank/big-bang/base:8.4

  - name: optional-feature
    required: false
    default: true
    files:
      - source: https://example.com/foo
        target: "/usr/local/bin/foo"
        shasum: 52299bd5a2df28b6a6ff9926e09abd0fa5e6c1094f5bb75b036a0452cfc00dfa
        executable: true

utilityCluster:
  repos:
    - https://repo1.dso.mil/platform-one/big-bang/[email protected]

  images:
    - registry1.dso.mil/ironbank/big-bang/base:8.4

Full Changelog

• Change zarf init to always install the docker registry by @jeff-mccoy in #82
  • Fix #83 by switching from zarf.localhost to 127.0.0.1 as the internal endpoint for the docker registry and Gitea
  • Update golang imports from the old Repo1 location to the new GitHub one
  • Update go deps versions
  • Rename the 3rd init option from utility-cluster to gitops-service

Compare: v0.11.0...v0.12.0

v0.11.0

🦄

What's Changed

New examples and an update to the zarf.yaml schema

⚠️ Contains breaking changes

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

⚠️ BREAKING: New schema for zarf.yaml config

The schema for the zarf.yaml config file has changed to allow optional components in Zarf deploy packages just like you can do in a Zarf init package

New:

kind: ZarfPackageConfig
metadata:
  name: foo
  description: "Foo example"

components:
  - name: baseline
    required: true
    manifests: manifests
    images:
      - registry1.dso.mil/ironbank/big-bang/base:8.4

  - name: optional-feature
    required: false
    default: true
    files:
      - source: https://example.com/foo
        target: "/usr/local/bin/foo"
        shasum: 52299bd5a2df28b6a6ff9926e09abd0fa5e6c1094f5bb75b036a0452cfc00dfa
        executable: true

utilityCluster:
  repos:
    - https://repo1.dso.mil/platform-one/big-bang/[email protected]

  images:
    - registry1.dso.mil/ironbank/big-bang/base:8.4

Previous:

kind: ZarfPackageConfig
metadata:
  name: foo
  description: "Foo example"

local:
  manifests: manifests

  files:
    - source: https://example.com/foo
      target: "/usr/local/bin/foo"
      shasum: 52299bd5a2df28b6a6ff9926e09abd0fa5e6c1094f5bb75b036a0452cfc00dfa
      executable: true

  images:
    - registry1.dso.mil/ironbank/big-bang/base:8.4

remote:
  repos:
    - https://repo1.dso.mil/platform-one/big-bang/[email protected]

  images:
    - registry1.dso.mil/ironbank/big-bang/base:8.4

New Example: Postgres Operator

A new example is available that creates a Zarf package that will deploy an example of a mostly production-ready Postgres database using Zarf's Applicance Mode. It comes with high availability, point-in-time backups, and periodic full backups. Comes with PGAdmin as a good demo of the proof of concept. Uses Zalando's postgres-operator.

New Example: Big Bang Core

A new example is available that creates a Zarf package that will deploy USAF Platform One's Big Bang Core to a Utility Cluster. This isn't normally the way you'd utilize a Utility Cluster, but it makes for a great easy to run demo. In a production scenario you would typically deploy a utility cluster separately from your main production workload cluster.

New Example: Utility Cluster

A new example is available that creates a Zarf package that will load a git repository and a container image into the Zarf Utility Cluster. It's a great way to test out the utility cluster while keeping the package super small, unlike the behemoth package that Big Bang Core ends up being.

Full changelog

• Add Postgres Operator Example (#50)
• Add backups to postgres-operator example (#52)
• Add Big Bang Core Example (#29)
• Fix makefile for postgres-operator example (#54)
• Update kafka tools URL (#57)
• Add resource requests and limits to Utility Cluster deployments (#59)
• Misc refactoring and cleanup (#61)
• Update Big Bang Core example with kubescape remediations (#62)
• Add kubescape to Big Bang Core example package (#60)
• Implement SHA256SUM validation (#65)
• Add zarf prepare sha256sum URL arg for remote SHASUM (#69)
• Upgrade Big Bang Core example to BB v1.17.0 (#67)
• BREAKING: Restructure zarf config yaml (#71)
• Docs and refactors for better kubescape scanning of BB example (#80)

Compare: v0.10.4...v0.11.0