You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
⚠️ BREAKING: The private container registry that zarf init deploys now requires auth
Packages 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 during package deploy and replaced with a properly formatted auth string, which is the base64 encoded username: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):
Now you can run zarf package deploy on remote packages.
Example:
# Naughty way
zarf package deploy https://example.com/some-package.tar.zst --insecure
# Good way
zarf package deploy https://example.com/some-package.tar.zst --shasum 15h1oi2h5ni1o2y5iunb1t25bui1t25gnu12n5
Full Changelog
Note: The v0.13.0 release was aborted due to a missing credential in the release pipeline. This release replaces v0.13.0 with the only change being referencing the new credential in the release pipeline yaml. We do it this way because we believe artifacts should be immutable.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
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 release was aborted due to a missing credential in the release pipeline. This release replaces v0.13.0 with the only change being referencing the new credential in the release pipeline yaml. 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.1.
Beta Was this translation helpful? Give feedback.
All reactions