image spec manifest annotations - key/platform/registry

[amartin120]

Please check below, if the PR fulfills these requirements:

• The commit message follows the guidelines.
• Tests for the changes have been added (for bug fixes / features).
• Docs have been added / updated (for bug fixes / features).

What kind of change does this PR introduce?

• 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>

Currently, the flags 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.

Moving forward, if I 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.

What is the current behavior?

• The only way to specify a global overrides to Hauler manifest is via the CLI flags.

What is the new behavior (if this is a feature change)?

• Allows for the same functionality but via a declarative approach.

Does this PR introduce a breaking change?

• No

Other information:

[amartin120]

https://github.com/rancherfederal/hauler/issues/153
https://github.com/rancherfederal/hauler/issues/172

[zackbradys]

Appreciate the quick fix @amartin120! I like that we are keeping the k8s theme with global flags being annotations in the manifest. 🚀