At the moment we're not able to verify the provenance of the kata-agent binaries that we consume as part of the build, i.e. we have to trust that there's no unexpected bins in the oci registry under the tag that we consume.
Short term solution:
Pin to oci digest, verify provenance manually when bumping the versions.
Long term solution:
Implement provenance generation in the kata oci publish process and verify it as part of the podvm image build process
mkulke
commented
1 month ago
At the moment we're not able to verify the provenance of the kata-agent binaries that we consume as part of the build, i.e. we have to trust that there's no unexpected bins in the oci registry under the tag that we consume.
Short term solution:
Pin to oci digest, verify provenance manually when bumping the versions.
Long term solution:
Implement provenance generation in the kata oci publish process and verify it as part of the podvm image build process