Fabiano Fidêncio df0cc78e57 kata-deploy-cc: Introduce the new kata-deploy for CC ...

Although I don't like the duplication introduced here, it's (at least
for now) way cleaner to have a specific daemonset for the Confidential
Containers effort.

As soon as we have all the bits and pieces upstreamed (kernel, QEMU, and
specific dependencies for each one of the TEEs), we'll be easily able to
get rid of this one.  However, for now, focusing on this different set
of files will make our lives easier.

This new daemonset includes the configurations needed for containerd in
order to use the `cc` specific `cri_handler`, which is not and will not
be upstream on the containerd side.

Note, CRI-O is **not** supported for now.

Fixes: #4620

Signed-off-by: Fabiano Fidêncio <fabiano.fidencio@intel.com>

2022-07-08 11:12:26 +02:00

..

scripts

kata-deploy-cc: Introduce the new kata-deploy for CC

2022-07-08 11:12:26 +02:00

Dockerfile

kata-deploy-cc: Introduce the new kata-deploy for CC

2022-07-08 11:12:26 +02:00