Open curx opened 2 years ago
Just to ensure we're talking about the same thing: https://blog.sigstore.dev/cosign-image-signatures-77bab238a93 this, right?
It does make sense to introduce something like that but I think we should first improve our naming and tagging, including the supporting pipeline. So far we only maintain a latest-greatest tag for each different flavour/dimension of the image
We should add some logic to keep tags for at least one "known good" and recent builds. And these should be signed.
Since the cosign can be used to verify container images are there any plans to do so and provide a cosign public key for validation?