mirror of
https://github.com/confidential-containers/confidential-containers.git
synced 2025-08-31 08:12:53 +00:00
9b797d0ddf
It's a known limitation that QEMU based runtime classes will not work with Kind or Minikube, leading to: ``` Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 42s default-scheduler Successfully assigned default/nginx-kata-qemu to minikube Warning FailedCreatePodSandBox 9s kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create containerd task: failed to create shim task: Failed to Check if grpc server is working: rpc error: code = DeadlineExceeded desc = timed out connecting to vsock 3189232285:1024: unknown ``` This needs further debug in order to get to the root cause of the issue, and potentially to a fix. However, for now, we should make sure that we document such limitation. One issue already reported about this is https://github.com/confidential-containers/operator/issues/124, and that's also been observed by Pradipta during the early tests of v0.1.0. Signed-off-by: Fabiano Fidêncio <fabiano.fidencio@intel.com>
Confidential Containers Documentation
Confidential Containers is an open source community working to leverage Trusted Execution Environments to protect containers and data and to deliver cloud native confidential computing.
We have a new release every 6 weeks! See Release Notes or Quickstart Guide
Our key considerations are:
- Allow cloud native application owners to enforce application security requirements
- Transparent deployment of unmodified containers
- Support for multiple TEE and hardware platforms
- A trust model which separates Cloud Service Providers (CSPs) from guest applications
- Least privilege principles for the Kubernetes cluster administration capabilities which impact delivering Confidential Computing for guest applications or data inside the TEE
Further Detail
Associated Repositories
- Kubernetes Operator for Confidential Computing : An operator to deploy confidential containers runtime (and required configs) on a Kubernetes cluster
License
