End users of coco prefers to provide either a encrypted or signed container image for their workload.
This feature will focus on the encrypted image support.

The encrypted container image may have the AI model embedded or their proprietary business logic. CoCo on ARO should be able to deploy workload with encrypted container images.

A problem we will face with encrypted images is if the image is accessed by the host (cri-o pulling the image): if cri-o can't decrypt it, it will return an error, and kubelet will stop the container creation process.
At the moment, there is no way to prevent cri-o from pulling the image, even if it is not used because the guest agent will pull it for itself. This needs to be addressed.