v0.13.2 #164
RothAndrew
announced in
Announcements
v0.13.2
#164
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Until we finish migrating from Repo1 to GitHub the release artifacts can be found HERE.
What's Changed
zarf init
deploys now requires authPackages will need to include
imagePullSecrets:
in their pod manifests and a corresponding regcred. See the Kubernetes documentation for more information. Using the special string###ZARF_DOCKERAUTH###
in your manifests will be automatically picked up by Zarf duringpackage deploy
and replaced with a properly formatted auth string, which is the base64 encodedusername:password
Here's an example of a valid Secret manifest for images that originated from Registry1 or DockerHub (K3s automatically redirects them to the private registry):
Deploy remote packages
Now you can run
zarf package deploy
on remote packages.Example:
Full Changelog
Note: The v0.13.0 and v0.13.1 releases were aborted due to a broken pipeline. This release replaces v0.13.0 with the only change being fixing the release pipeline. We do it this way because we believe artifacts should be immutable.
pre-commit
hookszarf version
commandkubescape
version in Big Bang Core example #111 - Update the version ofkubescape
in the Big Bang Core example--components
flag existgo.mod
to make VS Code happypre-commit run -a
on the whole codebase #151 - Runpre-commit run -a
an the codebaseThis discussion was created from the release v0.13.2.
Beta Was this translation helpful? Give feedback.
All reactions