Airgap Swiss Army Knife
Fixes a bug introduced in v1.0.2 that was smashing shared layers in the store/haul's index.json
along with a security patch. If you're running v1.0.2
please update to v1.0.3
a.s.a.p.
index.json
from cosign fork. - @amartin120Full Changelog: https://github.com/rancherfederal/hauler/compare/v1.0.2...v1.0.3
hauler store load
by @amartin120 in https://github.com/rancherfederal/hauler/pull/220
Full Changelog: https://github.com/rancherfederal/hauler/compare/v1.0.1...v1.0.2
hauler store load
by @amartin120 in https://github.com/rancherfederal/hauler/pull/220
Full Changelog: https://github.com/rancherfederal/hauler/compare/v1.0.1...v1.0.2-rc.1
Full Changelog: https://github.com/rancherfederal/hauler/compare/v1.0.0...v1.0.1
Full Changelog: https://github.com/rancherfederal/hauler/compare/v0.4.4...v1.0.0
Full Changelog: https://github.com/rancherfederal/hauler/compare/v0.4.3...v0.4.4
Hauler now allows for the use of key/platform/registry annotations for the image spec of a Hauler manifest. This gives users the ability to provide global overrides without the use of specifying flags via the CLI.
apiVersion: content.hauler.cattle.io/v1alpha1
kind: Images
metadata:
name: <name>
annotations:
hauler.dev/key: <cosign public key>
hauler.dev/platform: <platform>
hauler.dev/registry: <registry>
Flags passed from the CLI have a global effect on any image UNLESS it has a (key/platform) specified on the individual image. Individual image key/platform takes precedence.
If you have hauler.dev/key
and/or hauler.dev/platform
at the annotation level, it would work just like the CLI flag and globally apply for everything except individual images specifying otherwise. Just like above.
If you just so happen to provide both an annotation AND the CLI flag for the same thing, the CLI flag wins.
As for the hauler.dev/registry
annotation, it will apply globally unless the provided image reference already has a registry specified in its name.